Build page shows builds that fail gclient sync as green |
||||
Issue descriptionSeen on https://build.chromium.org/p/chromium.mac/builders/Mac10.10%20Tests (see screenshot). The most recent 30 builds have all failed gclient sync, yet most of them show as green (should be purple). Further, some of them fail both gclient sync AND browser_tests, and those show up as purple (should be red). It seems like the colour on this page is always one severity grade less than it should be?
,
Feb 17 2017
,
Feb 17 2017
How is "gclient sync failed" not a fatal error? Doesn't this mean we're building an out-of-date binary, or an up-to-date master with an out-of-date DEPS? Also from those logs: Error: 2> 2> ____ build at refs/remotes/origin/master 2> You have unstaged changes. 2> Please commit, stash, or reset. That's very bad...
,
Feb 17 2017
It's for the update_scripts step, which updates the infra tooling on the bot. If the infra tools are a few hours old everything else will still work. Syncing the chromium checkout is a different story and is fatal. That said, the current issue with update_scripts is known and a PSA was sent out about it.
,
Feb 17 2017
OK thanks.
,
May 15 2017
Closing this one for now; we aim to delete the update_scripts step entirely and I don't expect to do anything about this before then. |
||||
►
Sign in to add a comment |
||||
Comment 1 by estaab@chromium.org
, Feb 17 2017