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

Issue 921347 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 791061
Owner:
Closed: Jan 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

M72 Nightly Builders Failed on ManifestVersionSync:

Project Member Reported by kbleicher@google.com, Jan 12

Issue description

Last night's M72 build failed early on ManifestVersionSync:
https://logs.chromium.org/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8924560588310121920/+/steps/ManifestVersionedSync/0/stdout

I kicked off the builders again hoping it's transient but it's critical we get this cleared up to support an already late FSI for octopus.

I'll kick off a bug with similar.

Logs

cmd=['git', 'push', 'origin', 'temp_auto_checkin_branch:refs/heads/master'], cwd=/b/swarming/w/ir/cache/cbuild/repository/manifest-versions-internal
Traceback (most recent call last):
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/lib/failures_lib.py", line 230, in wrapped_functor
    return functor(*args, **kwargs)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 751, in PerformStage
    next_manifest = self.GetNextManifest()
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/stages/sync_stages.py", line 649, in GetNextManifest
    to_return = self.manifest_manager.GetNextBuildSpec(build_id=build_id)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/manifest_version.py", line 987, in GetNextBuildSpec
    raise GenerateBuildSpecException(last_error)
GenerateBuildSpecException: Failed to generate buildspec. error: return code: 1; command: git push origin temp_auto_checkin_branch:refs/heads/master
To https://chrome-internal.googlesource.com/chromeos/manifest-versions
 ! [rejected]                temp_auto_checkin_branch -> master (fetch first)
error: failed to push some refs to 'https://chrome-internal.googlesource.com/chromeos/manifest-versions'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

cmd=['git', 'push', 'origin', 'temp_auto_checkin_branch:refs/heads/master'], cwd=/b/swarming/w/ir/cache/cbuild/repository/manifest-versions-internal
 to fail.
 
Cc: dgarr...@chromium.org
The current build that I kicked off manually got past this step, so hopefully it was transient, but keeping bug open so it can be investigated.
Labels: -ReleaseBlock-Beta
Labels: -Pri-1 Pri-2
Cc: adurbin@chromium.org
Owner: jclinton@google.com
Jason, I'm not sure of the right owner or list to CC. Please assign accordingly. I think this might be a transient thing, but I wanted to put it on people's radar. 
Components: -Infra>Client>ChromeOS>Test Infra>Client>ChromeOS>CI
Mergedinto: 791061
Status: Duplicate (was: Untriaged)
It's transient 2 year old bug that has been solved on ToT; as these older branches decay off, the problem should go away entirely.

It looks like it was *just* fixed on ToT?  We'll be living with the 72 branch for another month or so.  Is it possible to CP this back to 72?  I don't know if it's wreaking havoc on 71, but maybe there too?

Sign in to add a comment