gsubtreed-mojo is failing. |
|||||||
Issue descriptionSeems we're failing to access to github.com. Adding Infra-Troopers label for triage. Error log: [I2016-07-10T17:15:04.131548+00:00 22861 140045442856704 infra.libs.git2.repo:231] Running ('git', 'push', 'origin', 'ff9b6c3da0ba00ed7f6ad83620a0fb546dad8075:refs/heads/master') remote: Permission to domokit/devtools.git denied to colinblundell. fatal: unable to access 'https://github.com/domokit/devtools/': The requested URL returned error: 403 [I2016-07-10T17:15:05.971269+00:00 22861 140045461747456 infra.libs.git2.repo:261] Finished in 1.9 sec [E2016-07-10T17:15:05.972107+00:00 22861 140045606885184 infra.services.gsubtreed.gsubtreed:107] FAILED push for 'mojo/devtools/common' [E2016-07-10T17:15:05.973049+00:00 22861 140045606885184 infra.services.gsubtreed.gsubtreed:109] Command ('git', 'push', 'origin', '91948c54058447914ff2f3a62f9ae4d6051f0886:refs/heads/master') returned non-zero exit status 128. remote: Permission to domokit/mojo_sdk.git denied to colinblundell. fatal: unable to access 'https://github.com/domokit/mojo_sdk/': The requested URL returned error: 403 [I2016-07-10T17:15:06.231775+00:00 22861 140045442856704 infra.libs.git2.repo:261] Finished in 2.1 sec [E2016-07-10T17:15:06.232311+00:00 22861 140045606885184 infra.services.gsubtreed.gsubtreed:107] FAILED push for 'mojo/public' [E2016-07-10T17:15:06.233026+00:00 22861 140045606885184 infra.services.gsubtreed.gsubtreed:109] Command ('git', 'push', 'origin', 'ff9b6c3da0ba00ed7f6ad83620a0fb546dad8075:refs/heads/master') returned non-zero exit status 128. [I2016-07-10T17:15:06.233782+00:00 22861 140045606885184 infra.libs.service_utils.outer_loop:85] End loop 0 (3.383482 sec) Build is broken: gsubtreed Revision range: Failing builders: gsubtreed-mojo: https://build.chromium.org/p/chromium.infra.cron/builders/gsubtreed-mojo
,
Jul 11 2016
Assign to infra git admin.
,
Jul 12 2016
This is still failing today.
,
Jul 12 2016
It will continue to fail until someone on chrome-infrastructure-team takes action on https://groups.google.com/a/google.com/d/msg/chrome-infrastructure-team/z04B0V2UnOg/pXSd3tJvDAAJ
,
Jul 12 2016
,
Jul 12 2016
Wrong bug, sorry.
,
Jul 12 2016
vtl@ and jamesr@ have been granted access. Let me know if you need anything else.
,
Jul 13 2016
It's too vague for a git admin request. I'm keeping it as a trooper issue though.
,
Jul 13 2016
@stip - the access we've been granted is 'reader' access, which is not useful as we need to put a new token in the valentine entry to make the bot succeed. I replied on the thread a few hours ago.
,
Jul 18 2016
We still appear to have only 'reader' access and are thus still blocked on getting 'writer' access in order to place a new access token in valentine and fix the bot.
,
Jul 18 2016
OK, an updated access token is now in valentine. According to the document what needs to happen now is "the netrc github password token in the netrc eyaml file be updated in puppet" needs to be updated to this value and then the mirror needs to be re-enabled.
,
Jul 20 2016
Adding Sheriff-Chromium label since failures are shown on sheriff-o-matic.
,
Jul 20 2016
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/1595e52c30ec601c549d1f5af4718751f40b3583 commit 1595e52c30ec601c549d1f5af4718751f40b3583 Author: smut <smut@google.com> Date: Wed Jul 20 22:24:05 2016
,
Jul 20 2016
https://build.chromium.org/p/chromium.infra.cron/builders/gsubtreed-mojo/builds/74684 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by yukishiino@chromium.org
, Jul 11 2016