cbuildbot always fails unless using --do-not-use-buildbucket |
||
Issue descriptionSee for example: https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10496 https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10497 Those were launched with something like: $ cbuildbot --remote --profile=aosp -g *354727 amd64-generic-cheets-release Note that this is a draft CL, but that's not the issue, that bot failed too, and it was just ToT: https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10487 Passing --do-not-use-buildbucket works around the issue: https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10499
,
Apr 14 2017
I'm wondering if this was a transient issue unrelated to buildbucket. Re-running a tryjob now, just to see.
,
Apr 14 2017
I don't think this is buildbucket related. My tryjob just passed, even though it was launched that way. https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/10534
,
Apr 15 2017
An overnight tryjob worked for me too. Agreed, looks like a transient issue. |
||
►
Sign in to add a comment |
||
Comment 1 by dgarr...@chromium.org
, Apr 14 2017