Issue metadata
Sign in to add a comment
|
ERROR: missing Change-Id in message footer |
||||||||||||||||||||||||
Issue descriptionMany builds (all Full & Release builders) are generating StatusUpdateExceptions in MasterSlaveSyncCompletion or CanaryCompletion phase. They are generating these exceptions even in otherwise green builds. Red build examples: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8925922367261625728 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8925896257723672848 Green build with CanaryCompletion failures, still marked green: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8925922376548966416 The error seen is: cmd=['git', 'push', 'origin', 'temp_auto_checkin_branch:refs/for/master%submit'], cwd=/b/swarming/w/ir/cache/cbuild/repository/manifest-versions[0m [1;31m08:16:05: ERROR: Retrying to update the status: Retry 1/20[0m 08:16:05: INFO: Updating manifest-versions checkout. 08:16:10: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/for/master%submit', project_name=None)) with message: Automatic checkin: status=pass build_version 11483.0.0-rc1 for amd64-generic-full [1;31m08:16:11: ERROR: Failed to update the status for amd64-generic-full during remote command: return code: 1; command: git push origin temp_auto_checkin_branch:refs/for/master%submit remote: remote: Processing changes: refs: 1 remote: Processing changes: refs: 1, done remote: ERROR: commit 91d9336: missing Change-Id in message footer remote: remote: Hint: to automatically insert a Change-Id, install the hook: remote: f=`git rev-parse --git-dir`/hooks/commit-msg ; curl -Lo $f https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x $f remote: and then amend the commit: remote: git commit --amend remote: Finally, push your changes again remote: To https://chromium.googlesource.com/a/chromiumos/manifest-versions ! [remote rejected] temp_auto_checkin_branch -> refs/for/master%submit (commit 91d9336: missing Change-Id in message footer) error: failed to push some refs to 'https://chromium.googlesource.com/a/chromiumos/manifest-versions'
,
Dec 29
This is the first build run exhibiting this error: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927106603413760816 which makes me think it was likely caused by this chumped commit: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1378909
,
Dec 29
,
Dec 29
,
Jan 2
The initial report is something new; perhaps a Gerrit flake. Comment 1, however, is unrelated and is another example of issue 791061 .
,
Jan 4
I think the chump here: https://chromium-review.googlesource.com/c/chromiumos/chromite/+/1394573 Is causing these errors in the CQ: https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8925309464790329088/+/steps/CommitQueueSync/0/stdout 15:55:18: INFO: Translating result <class 'chromite.cbuildbot.manifest_version.GenerateBuildSpecException'>: Failed to generate LKGM Candidate. error: return code: 1; command: git push origin temp_auto_checkin_branch:refs/for/master%submit To https://chromium.googlesource.com/a/chromiumos/manifest-versions ! [remote rejected] temp_auto_checkin_branch -> refs/for/master%submit (commit dcc264a: missing Change-Id in message footer) error: failed to push some refs to 'https://chromium.googlesource.com/a/chromiumos/manifest-versions'
,
Jan 4
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by cjmcdonald@chromium.org
, Dec 28