New issue
Advanced search Search tips

Issue 891542 link

Starred by 2 users
Status: Duplicate
Merged: issue 791061
Owner:
jclinton@chromium.org
Closed: Oct 3
Cc:
apronin@chromium.org
yamaguchi@chromium.org
jclinton@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

CanaryCompletion: Failed to update the status during //..// git push

Project Member Reported by briannorris@chromium.org, Oct 2 
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8933755022180879184

15:22:00: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/heads/master', project_name=None)) with message: Automatic checkin: status=pass build_version 11121.0.0 for cheza-release 
15:22:00: ERROR: Failed to update the status for cheza-release during remote command: cmd=['git', 'push', 'origin', 'temp_auto_checkin_branch:refs/heads/master'], cwd=/b/swarming/w/ir/cache/cbuild/repository/manifest-versions-internal
15:22:00: ERROR: Retrying to update the status:  Retry 1/20
15:22:00: INFO: Updating manifest-versions checkout.
15:22:33: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/heads/master', project_name=None)) with message: Automatic checkin: status=pass build_version 11121.0.0 for cheza-release 
15:22:33: ERROR: Failed to update the status for cheza-release during remote command: cmd=['
[...]



It's not clear what exactly failed in the 'git push', so I'm not sure if this is actionable yet. But it would be good to at least improve the logging, so future issues can be better understood. Do we need both e.message and e.result? Or just log 'e' (the whole error object)?

Comment 1 by briannorris@chromium.org, Oct 2

Cc: apronin@chromium.org

Comment 2 by briannorris@chromium.org, Oct 2 

Issue 891543 has been merged into this issue.

Comment 3 by apronin@chromium.org, Oct 2 

From issue 891543: it's not just cheza. The same error seen at least for monroe and mccloud

Comment 4 by apronin@chromium.org, Oct 2

Cc: jclinton@chromium.org

Comment 5 by briannorris@chromium.org, Oct 2

Cc: -jclinton@chromium.org
Summary: CanaryCompletion: Failed to update the status for cheza-release during //..// git push (was: cheza-release: CanaryCompletion: Failed to update the status for cheza-release during //..// git push)

Comment 6 by briannorris@chromium.org, Oct 2

Cc: jclinton@chromium.org

Comment 7 by briannorris@chromium.org, Oct 2

Summary: CanaryCompletion: Failed to update the status during //..// git push (was: CanaryCompletion: Failed to update the status for cheza-release during //..// git push)

Comment 8 by briannorris@chromium.org, Oct 3

Cc: yamaguchi@chromium.org
Labels: -Pri-2 Pri-1
Owner: jclinton@chromium.org
Status: Assigned (was: Untriaged)
Yeah...there are a lot of release failures that failed with this. Unless we think this was a transient failure, it seems like this should be high priority.

You can see our annotations that point several release build failures to this:

https://chromiumos-build-annotator.googleplex.com/build_annotations/edit_annotations/master-release/2998443/

Comment 9 by jclinton@chromium.org, Oct 3

Mergedinto: 891352
Status: Duplicate (was: Assigned)
Almost certainly related to the GoB/Gerrit outage today.

Comment 10 by jclinton@chromium.org, Oct 4

Mergedinto: -891352 791061
This wasn't the GoB outage; it was another example of canary slaves racing to update manifest-versions-internal.
►

Sign in to add a comment