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

Issue 646160 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

R54 daisy builders fail ManifestVersionedSync

Project Member Reported by tienchang@chromium.org, Sep 12 2016

Issue description

daisy builders do not have successful builds, due to ManifestVersionedSync:

21:13:54: ERROR: <class 'chromite.cbuildbot.repository.SrcCheckOutException'>: return code: 1; command: repo --time sync -n
cwd=/b/cbuild/shared_internal
Traceback (most recent call last):
  File "/tmp/cbuildbot-tmpju0UKw/tmp6ZjlRi/chromite/cbuildbot/failures_lib.py", line 172, in wrapped_functor
    return functor(*args, **kwargs)
  File "/tmp/cbuildbot-tmpju0UKw/tmp6ZjlRi/chromite/cbuildbot/stages/sync_stages.py", line 762, in PerformStage
    self.ManifestCheckout(new_manifest)
  File "/tmp/cbuildbot-tmpju0UKw/tmp6ZjlRi/chromite/cbuildbot/stages/sync_stages.py", line 416, in ManifestCheckout
    self.repo.Sync(next_manifest)
  File "/tmp/cbuildbot-tmpju0UKw/tmp6ZjlRi/chromite/cbuildbot/repository.py", line 476, in Sync
    raise SrcCheckOutException(err_msg)
SrcCheckOutException: return code: 1; command: repo --time sync -n
cwd=/b/cbuild/shared_internal

https://chromegw.corp.google.com/i/chromeos_release/builders/daisy-release%20release-R54-8743.B
 
Looks like repo sync failed
Cc: dshi@chromium.org nxia@chromium.org
Owner: jrbarnette@chromium.org
The cause is visible further up. Looks like it's the GoB kernel sync bug. If someone has that bug number, can we dup this?

Fetching project chromeos/overlays/overlay-amd64-generic-goofy-private
Fetching project chromeos/overlays/overlay-variant-veyron-jerry-private
From https://chromium.googlesource.com/a/chromiumos/overlays/chromiumos-overlay
   4af65b0..d16e6b6  release-R54-8743.B -> cros/release-R54-8743.B
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
error: Cannot fetch chromiumos/third_party/kernel

error: Exited sync due to fetch errors
real	1m49.268s
21:10:13: WARNING: cmd ['repo', '--time', 'sync'] failed, clean up repository and retry sync.
21:10:19: INFO: RunCommand: repo manifest in /b/cbuild/shared_internal
21:10:19: 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 release-R54-8743.B in /b/cbuild/shared_internal

repo has been initialized in /b/cbuild/shared_internal
21:10:20: INFO: RunCommand: repo --time sync -n in /b/cbuild/shared_internal
Fetching project chromeos/overlays/overlay-slippy-private

Comment 3 by nxia@chromium.org, Sep 12 2016

It can be consistently reproduced by running "repo --time sync -n" inside build machine. Looks like it's not a GOB issue, as other builds don't have this issue around that time. 

Doing sync tests on that machine. 
Cc: trapti@chromium.org

Comment 5 by nxia@chromium.org, Sep 12 2016

Manually removed the kernel repository in the builder. Successfully run ' repo --time sync -n' in the builder. 

You can either trigger a new build or wait for the next scheduled build. NO need to clobber the build I guess.

Comment 6 by dchan@chromium.org, Sep 19 2016

will monitor the next 2 build and mark as fixed accordingly.
Status: Fixed (was: Assigned)

Comment 8 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 9 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 10 by dchan@google.com, May 30 2017

Labels: VerifyIn-60
Labels: VerifyIn-61

Comment 12 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment