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

Issue 805122 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: ----



Sign in to add a comment

bot_update failing on multiple builders

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jan 23 2018

Issue description

Comment 1 by joedow@chromium.org, Jan 23 2018

Labels: Infra-Troopers
Possibly related to  crbug.com/805122 

Comment 2 by joedow@chromium.org, Jan 23 2018

Components: Infra

Comment 3 by kbr@chromium.org, Jan 23 2018

Cc: kbr@chromium.org

Comment 4 by kbr@chromium.org, Jan 23 2018

 Issue 805121  has been merged into this issue.

Comment 5 by kbr@chromium.org, Jan 23 2018

Issue 805096 has been merged into this issue.

Comment 6 by kbr@chromium.org, Jan 23 2018

Components: -Infra Internals>GPU>Testing Infra>Client>Chrome
Owner: jrobbins@chromium.org
Status: Assigned (was: Available)
All seem to be failing for the following repo:
https://chrome-internal.googlesource.com/chrome/app-streaming/

Complaining with "Git repository not found". Seems to be a backend issue in the git servers.

As a P0, assigning directly to trooper. Jason, have you reached out to the gob team?
Labels: -Pri-0 Pri-1
Easy come, easy go. It looks like whatever caused the git errors was transient. All the affected builders have since passed a subsequent bot_update.
I see recent successes on each of the builders listed in the issue description.
I didn't make any change.

Status: Fixed (was: Assigned)
I checked again and they are still mainly green.  So, I think this was a transient problem.
Issue 805081 has been merged into this issue.

Sign in to add a comment