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

Issue 625017 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

Build failure: gsubtreed-mojo

Project Member Reported by horo@chromium.org, Jul 1 2016

Issue description

Build is broken:
gsubtreed

Revision range:

Failing builders:
gsubtreed-mojo: https://build.chromium.org/p/chromium.infra.cron/builders/gsubtreed-mojo


 

Comment 1 by horo@chromium.org, Jul 1 2016

Cc: vadimsh@chromium.org friedman@chromium.org blundell@chromium.org

Comment 2 by horo@chromium.org, Jul 1 2016

Cc: aga...@chromium.org
Cc: p...@chromium.org viettrungluu@chromium.org
+viettrunglu@, ppi@

Is the github Mojo project still making using of the mirroring that this bot is doing?
OK, so the failure is because I got removed as a member of the domokit github organization yesterday, and that bot is pushing changes with my username.

I've instructed the Chromium sheriff to turn off the bot for now. If it's still needed then someone active on the Mojo github project will need to take it over, switch things over to using their username, and restart it. Instructions are here: https://docs.google.com/document/d/1ywaftmfn-mWaEctLDPaYOWj2Ixn5OSFjQS2Pcht-InA/edit#heading=h.6dq67lh4qm5x.
I asked a trooper to turn off the bot here: https://bugs.chromium.org/p/chromium/issues/detail?id=625085
We are depending on those mirrors.
We have an updated access token, but none of us on the team have access to valentine to put the token in for infra to pick up.  vtl@ has sent a request to chrome-infrastructure-team@ as the linked doc recommends.

Comment 8 by jwd@chromium.org, Jul 6 2016

Any update on getting the token into valentine?

Comment 9 by jam...@chromium.org, Jul 11 2016

We're still waiting on chrome-infrastructure-team@ to grant access to that valentine entry so we can add a token.  The last email on the thread added agable@ and vadimsh@ to the thread, so I'm guessing the action item is on one of them.
Owner: aga...@chromium.org
Status: Fixed (was: Available)
I just got back from vacation and just took care of this. jamesr@ and vtl@ should now have 'writer' access.
I put the token in valentine and replied on the chrome-infrastructure-team@ thread with further instructions (which involve copying those tokens somewhere that is described in the doc but possibly shouldn't be listed on a publicly viewable bug).  It doesn't appear that those instructions have been followed and the bot is still red.
It's green now.

Sign in to add a comment