Issue metadata
Sign in to add a comment
|
Master PFQ failed with GenerateBuildSpecException error |
||||||||||||||||||||||||
Issue descriptionSee 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.
,
Dec 21
Jason, did your recent changes to how we push manifest-versions changes affect this workflow?
,
Dec 21
this is unrelated to issue 913317. this is like issue 791061 .
,
Dec 21
No, not related because the cmd doesn't have the automerge remote ref as the push destination.
,
Dec 21
,
Dec 28
master-paladin failed with the same error. https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8925896472368159536
,
Dec 28
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 |
|||||||||||||||||||||||||
Comment 1 by x...@chromium.org
, Dec 21