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

Issue 917421 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 791061
Owner:
Closed: Dec 28
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 791061



Sign in to add a comment

Master PFQ failed with GenerateBuildSpecException error

Project Member Reported by x...@chromium.org, Dec 21

Issue description

See https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8926553306670561712

Error message:
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 863, in GetNextManifest
    build_id=build_id)
  File "/b/swarming/w/ir/cache/cbuild/repository/chromite/cbuildbot/lkgm_manager.py", line 427, in CreateNewCandidate
    raise manifest_version.GenerateBuildSpecException(last_error)
GenerateBuildSpecException: Failed to generate LKGM Candidate. 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


It looks like an Infra failure. 
 
Cc: vapier@chromium.org steve...@chromium.org
I'm wondering if it's related to Issue 913317. 
Cc: jclinton@chromium.org
Owner: jclinton@chromium.org
Jason, did your recent changes to how we push manifest-versions changes affect this workflow?
Blockedon: 791061
Cc: -vapier@chromium.org -steve...@chromium.org
this is unrelated to issue 913317.  this is like  issue 791061 .
Owner: dgarr...@chromium.org
Status: Assigned (was: Untriaged)
No, not related because the cmd doesn't have the automerge remote ref as the push destination.
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
Mergedinto: 791061
Status: Duplicate (was: Assigned)
This is another code path where we should use the automerge feature since any one path not using automerge still has to contend with other merges. I'll merge this bug to  issue 791061  and track doing that there.

Sign in to add a comment