Issue metadata
Sign in to add a comment
|
master-paladin CQ failing on internal-manifests (cbuild_launch) |
||||||||||||||||||||||||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win10, MacOS 10.12, etc...) What steps will reproduce the problem? (1) CQ fails to update manifest-versions in cbuild_launch phase (2) (3) What is the expected result? What happens instead? master-paladin CQ fails to get going: 18:15:58: ERROR: 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. Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. failed buils: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927112761877344480 logs here: https://logs.chromium.org/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8927112761877344480/+/steps/CommitQueueSync/0/stdout |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by jclinton@chromium.org
, Dec 15Status: Duplicate (was: Untriaged)