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

Issue 918201 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

ERROR: missing Change-Id in message footer

Project Member Reported by cjmcdonald@chromium.org, Dec 28

Issue description

Many 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
08:16:05: ERROR: Retrying to update the status:  Retry 1/20
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 
08: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'

 
The error in the Release builders looks like:

cmd=['git', 'push', 'origin', 'temp_auto_checkin_branch:refs/heads/master'], cwd=/b/swarming/w/ir/cache/cbuild/repository/manifest-versions-internal
03:14:24: ERROR: Retrying to update the status:  Retry 1/20
03:14:24: INFO: Updating manifest-versions checkout.
03:15:10: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/heads/master', project_name=None)) with message: Automatic checkin: status=pass build_version 11151.85.0 for grunt-release 
03:15:10: ERROR: Failed to update the status for grunt-release during remote command: 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.
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
Cc: jclinton@chromium.org
Cc: djkurtz@chromium.org
Labels: -Pri-1 Pri-2
Status: Available (was: Untriaged)
The initial report is something new; perhaps a Gerrit flake. Comment 1, however, is unrelated and is another example of  issue 791061 .

Summary: ERROR: missing Change-Id in message footer (was: StatusUpdateException in many builders)
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'
Mergedinto: 791061
Status: Duplicate (was: Available)

Sign in to add a comment