New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 724874 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Build wedged/endless-loop on master-paladin CommitQueueSync

Project Member Reported by davidri...@chromium.org, May 21 2017

Issue description

The following build got stuck for at least three hours in the CommitQueueSync stage.
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/14667

Seems to be repeatedly syncing:
real	0m34.380s
06:57:54: INFO: RunCommand: repo --time sync --force-sync '--cache-dir=/b/build/slave/cache/git' -l in /b/cbuild/repository
Your sources have been sync'd successfully.
real	0m5.179s
06:58:00: INFO: Waiting for new CLs (37 minutes left)...
06:58:30: INFO: RunCommand: repo manifest in /b/cbuild/repository
06:58:30: INFO: RunCommand: repo init --repo-url https://chromium.googlesource.com/external/repo --manifest-url https://chrome-internal-review.googlesource.com/chromeos/manifest-internal --manifest-name official.xml --manifest-branch master in /b/cbuild/repository
repo has been initialized in /b/cbuild/repository
06:58:31: INFO: RunCommand: repo sync --help in /b/cbuild/repository
06:58:31: INFO: RunCommand: repo --time sync --force-sync '--cache-dir=/b/build/slave/cache/git' -n in /b/cbuild/repository
--

The Waiting for new CLs line appears every minute or so:
03:41:15: INFO: Waiting for new CLs (234 minutes left)...
03:42:26: INFO: Waiting for new CLs (233 minutes left)...
03:43:37: INFO: Waiting for new CLs (232 minutes left)...

 
I've killed the build.
Status: WontFix (was: Untriaged)
Ooops.  Didn't realize that the CQ was actually waiting for new changes to test and WAI. 

Sign in to add a comment