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

Issue 913470 link

Starred by 1 user
Status: Duplicate
Merged: issue 791061
Owner: ----
Closed: Dec 10
Cc:
█ kbleicher@chromium.org
vapier@chromium.org
athilenius@chromium.org
█ djmm@chromium.org
█ josa...@chromium.org
█ gu...@chromium.org
jclinton@chromium.org
█ bhthompson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

M71 Master Builder Failing on temp_auto_checkin_branch

Project Member Reported by kbleicher@google.com, Dec 10 
The last M71 build failed on the CanaryCompletion stage; we're going to need a new M71 today to serve as a beta / stable.

Logs: https://logs.chromium.org/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8927554063077362800/+/steps/CanaryCompletion/0/stdout

ERROR: Failed to update the status for master-release during remote command: return code: 1; command: git push origin temp_auto_checkin_branch:refs/heads/master

failed to push some refs to 'https://chrome-internal.googlesource.com/chromeos/manifest-versions'

Comment 1 by bhthompson@google.com, Dec 10

Cc: vapier@chromium.org

Comment 2 by jclinton@chromium.org, Dec 10

Mergedinto: 791061
Status: Duplicate (was: Untriaged)
This is a recurrence of  issue 791061 . It will almost certainly succeed on the next run. I've kicked of another run now: https://luci-scheduler.appspot.com/jobs/chromeos/release-R71-11151.B-master-release/9092938156021044224
►

Sign in to add a comment