New issue
Advanced search Search tips

Issue 905726 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

kalista-release: git push failed

Project Member Reported by zwisler@google.com, Nov 15

Issue description

Failing build (which was previously green):

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8929798957203341728

Relevant error messages:

06:39:15: INFO: Updating manifest-versions checkout.
06:40:55: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/heads/master', project_name=None)) with message: Automatic checkin: status=pass build_version 11264.0.0 for kalista-release 
06:40:56: ERROR: Failed to update the status for kalista-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.
 
Mergedinto: 791061
Status: Duplicate (was: Untriaged)

Sign in to add a comment