Issue metadata
Sign in to add a comment
|
ensure_goma.ensure_installed flaky on chromium.perf on Win 7 Low-End Perf |
||||||||||||||||||||
Issue descriptionRevision range first seen: Link to failing step log: https://build.chromium.org/p/chromium.perf/builders/Win%207%20Low-End%20Perf%20%281%29?numbuilds=200 https://build.chromium.org/p/chromium.perf/builders/Win%207%20Low-End%20Perf%20%282%29?numbuilds=200 Possibly related: https://bugs.chromium.org/p/chromium/issues/detail?id=605403 Snippet from log: [P2824 04:25:09.441 service.go:71 W] Failed to load private key JSON - open C:\creds\service_accounts\service-account-goma-client.json: The system cannot find the path specified. [P2824 04:25:09.441 auth.go:593 W] Failed to mint a token: invalid service account credentials [P2824 04:25:09.441 remote.go:103 W] cipd: connectivity error (Get https://chrome-infra-packages.appspot.com/_ah/api/repo/v1/instance/resolve?package_name=infra_internal%2Fgoma%2Fclient%2Fwindows-amd64&version=release: invalid service account credentials) Error: request to the backend failed after multiple attempts. step returned non-zero exit code: 1 +phajdan.jr since you're looking at the other bug. Another thing to notice is that even though that (sub) step is failing, the overall build is still declared successful. Not sure if that's intentional.
,
May 10 2016
Friendly sheriff ping (According to the Perf Bot Sheriffing guide, Pri-1 build bot bugs should be pinged daily. Please close the issue if it's already been fixed or lower its priority.) This is still flaky on windows bot https://build.chromium.org/p/chromium.perf/builders/Win%207%20Low-End%20Perf%20(2)
,
May 25 2016
,
May 25 2016
Since this is an auth issue does infra labs know what to do here?
,
May 25 2016
,
May 27 2016
Fixed up puppet on the affected hosts. Errors are now gone. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by qyears...@chromium.org
, May 5 2016