Sync chrome stage marked as failed though chrome is synched |
||||||||||||||
Issue descriptionLink to sample build: https://uberchromegw.corp.google.com/i/chromeos_release/builders/daisy-release%20release-R52-8350.B/builds/47 Logs link: https://uberchromegw.corp.google.com/i/chromeos_release/builders/daisy-release%20release-R52-8350.B/builds/47/steps/SyncChrome/logs/stdio @@@STEP_FAILURE@@@ 12:49:01: ERROR: <class 'chromite.lib.cros_build_lib.RunCommandError'>: return code: 1; command: /b/cbuild/shared_internal/chromite/bin/sync_chrome --reset --internal --tag 52.0.2743.75 /b/cbuild/shared_internal/.cache/distfiles/target/chrome-src-internal cwd=/b/cbuild/shared_internal Traceback (most recent call last): File "/b/cbuild/shared_internal/chromite/cbuildbot/failures_lib.py", line 160, in wrapped_functor return functor(*args, **kwargs) File "/b/cbuild/shared_internal/chromite/cbuildbot/stages/chrome_stages.py", line 111, in PerformStage useflags, **kwargs) File "/b/cbuild/shared_internal/chromite/cbuildbot/commands.py", line 2429, in SyncChrome retry_util.RunCommandWithRetries(constants.SYNC_RETRIES, cmd, cwd=build_root) File "/b/cbuild/shared_internal/chromite/lib/retry_util.py", line 208, in RunCommandWithRetries return RetryCommand(cros_build_lib.RunCommand, max_retry, *args, **kwargs) File "/b/cbuild/shared_internal/chromite/lib/retry_util.py", line 180, in RetryCommand return GenericRetry(ShouldRetry, max_retry, functor, *args, **kwargs) File "/b/cbuild/shared_internal/chromite/lib/retry_util.py", line 88, in GenericRetry ret = functor(*args, **kwargs) File "/b/cbuild/shared_internal/chromite/lib/cros_build_lib.py", line 619, in RunCommand raise RunCommandError(msg, cmd_result) RunCommandError: return code: 1; command: /b/cbuild/shared_internal/chromite/bin/sync_chrome --reset --internal --tag 52.0.2743.75 /b/cbuild/shared_internal/.cache/distfiles/target/chrome-src-internal cwd=/b/cbuild/shared_internal
,
Jul 13 2016
Just a note... the sync errors are happening on a number of builders, including physical ones that have previously been able to sync Chrome on this branch without errors. https://uberchromegw.corp.google.com/i/chromeos_release/builders/auron-release%20release-R52-8350.B
,
Jul 13 2016
Assigning to this week's deputy.
,
Jul 13 2016
________ running 'git -c core.deltaBaseCacheLimit=2g fetch origin --verbose' in '/b/cbuild/shared_internal/.cache/distfiles/target/chrome-src-internal/src/third_party/skia' [0:02:12] error: refs/remotes/origin/chrome/try/cg does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/fix does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/gdi does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/longlong does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/try-pic does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/typometrics does not point to a valid object! [0:02:12] error: refs/remotes/origin/gasp_test does not point to a valid object! [0:02:12] error: refs/remotes/origin/temp/text_size does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/scalercontext does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/text_size does not point to a valid object! [0:02:12] error: refs/tags/chrome/2138 does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/cg does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/fix does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/gdi does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/longlong does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/try-pic does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/typometrics does not point to a valid object! [0:02:12] error: refs/remotes/origin/gasp_test does not point to a valid object! [0:02:12] error: refs/remotes/origin/temp/text_size does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/scalercontext does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/text_size does not point to a valid object! [0:02:12] error: refs/tags/chrome/2138 does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/cg does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/fix does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/gdi does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/longlong does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/try-pic does not point to a valid object! [0:02:12] error: refs/remotes/origin/chrome/try/typometrics does not point to a valid object! [0:02:12] error: refs/remotes/origin/gasp_test does not point to a valid object! [0:02:12] error: refs/remotes/origin/temp/text_size does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/scalercontext does not point to a valid object! [0:02:12] error: refs/remotes/origin/try/text_size does not point to a valid object! [0:02:12] error: refs/tags/chrome/2138 does not point to a valid object! Similar to https://bugs.chromium.org/p/chromium/issues/detail?id=627124.
,
Jul 13 2016
Could be git corruption, SyncChrome stage is really flaky on 52.
,
Jul 13 2016
Don, we fix that one by running a force build with clobber. Should we do a clobber here too?
,
Jul 13 2016
How many builders are you planning to clobber? Should be good for about 10 at a time.
,
Jul 13 2016
17 builders have this issue: https://uberchromegw.corp.google.com/i/chromeos_release/builders/ I will start to clobber 10 at a time.
,
Jul 13 2016
First 10 to clobber is: https://uberchromegw.corp.google.com/i/chromeos_release/builders/auron-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/clapper-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/daisy-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/glados-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/guado_moblab-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/jecht-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/kunimitsu-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/nyan_big-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/oak-release%20release-R52-8350.B/ https://uberchromegw.corp.google.com/i/chromeos_release/builders/parrot-release%20release-R52-8350.B/
,
Jul 14 2016
Last 7 to clobber is: https://uberchromegw.corp.google.com/i/chromeos_release/builders/peach_pit-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/peppy-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/samus-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/stout-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/strago-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/veyron_pinky-release%20release-R52-8350.B https://uberchromegw.corp.google.com/i/chromeos_release/builders/x86-mario-release%20release-R52-8350.B
,
Jul 14 2016
Close it, since all failed builders passed the SyncChromeStage
,
Aug 29 2016
,
Oct 7 2016
,
Nov 19 2016
,
Jan 21 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 by gkihumba@chromium.org
, Jul 13 2016