My favorites ▼ | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 206521: chrome PFQ builds consistently fail in "Clear and Clone chromite" step
1 person starred this issue and may be notified of changes. Back to list
Status:  Verified
Moved from:  issue chromium-os:23528
Owner:  sosa@chromium.org
Closed:  Nov 2011


Sign in to add a comment
 
Project Member Reported by e...@chromium.org, Nov 29, 2011 
http://chromegw.corp.google.com/i/chromiumos/builders/arm%20generic%20chrome%20PFQ/builds/432/steps/Clear%20and%20Clone%20chromite/logs/stdio

fails with 

   error: pathspec 'releases' did not match any file(s) known to git.
Nov 29, 2011
#1 e...@chromium.org 
An additional data point: the failures seem to occur after a commit by "chrome-release". E.g., 

Changed by: chrome-release@google.com
Changed at: Tue 29 Nov 2011 02:39:46
Branch: releases
Revision: 111902 
Changed files:

17.0.954.0
Comments:
Tagging release 17.0.954.0
Properties:
Changed by: chrome-release@google.com
Changed at: Tue 29 Nov 2011 02:39:46
Branch: releases
Revision: 111903 
Changed files:

17.0.954.0/DEPS
Comments:
Publish DEPS file for Chromium 17.0.954.0 
Properties:
Summary: chrome PFQ builds sporadically fail in "Clear and Clone chromite" step
Nov 29, 2011
#3 stevenjb@chromium.org 
Also had the pattern of 'Changed by: chrome-release@google.com'

Output from stage ends with:

error: pathspec 'releases' did not match any file(s) known to git.
program finished with exit code 1
elapsedTime=11.093850
Nov 29, 2011
#4 davidjames@google.com 
The following CL broke this:

  http://codereview.chromium.org/8669004

Specifically, the issue is that the following case was removed:
 # Whitelist top of tree chrome PFQ builds to always use master
 # as the branch checkout, this avoids us trying to clone a SVN	
 # revision that is passed to the builder. We are doing this in this	
 # fashion to avoid having to write a script that wraps our git call	
 # to confirm the hash we are passed. While technically we have access to	
 # branch/revision unfortunately the only way it is available is via	
 # WithProperties which is only transferred to something usable in a shell	
 # step.
Summary: chrome PFQ builds consistently fail in "Clear and Clone chromite" step
Status:
Owner: sosa@chromium.org
Nov 29, 2011
#5 sosa@chromium.org 
(No comment was entered for this change.)
Status: Assigned
Labels: Iteration-44
Nov 30, 2011
#6 sosa@chromium.org 
Fixed in http://codereview.chromium.org/8734004 with external master restart.
Status: Fixed
Dec 6, 2011
#7 kr...@chromium.org 
(No comment was entered for this change.)
Status: Verified
Mar 6, 2013
#8 bugdroid1@chromium.org 
(No comment was entered for this change.)
Labels: OS-Chrome
Mar 9, 2013
#9 bugdroid1@chromium.org 
(No comment was entered for this change.)
Labels: -Area-Build -TreeCloser -Team-BuildRelease Build Hotlist-TreeCloser
► Sign in to add a comment

Powered by Google Project Hosting