achuith@, bpastene@ do you think this is related to crbug.com/913317 (and crbug.com/913744 ) ?
Build page:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8927330250481291648
Log:
08:26:45: INFO: Updating manifest-versions checkout.
08:27:34: INFO: Not generating blamelist for lkgm as it is not appropriate for this build type.
08:27:48: INFO: Publishing build spec for: 11391.0.0-rc1
08:27:48: INFO: Publishing with commit message: Automatic: Start master-chromium-pfq master 11391.0.0-rc1
CrOS-Build-Id: 3221355
08:27:57: INFO: Pushing to branch (_RemoteRef(remote='origin', ref='refs/heads/master', project_name=None)) with message: Automatic: Start master-chromium-pfq master 11391.0.0-rc1
CrOS-Build-Id: 3221355
[1;31m08:27:57: 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.
Comment 1 by vapier@chromium.org
, Dec 12Status: Duplicate (was: Available)