daisy-paladin succeeded but was rerun by buildbucket |
||||
Issue descriptiondaisy-paladin failed, didn't get retried by cq-master and didn't show up in cq-master failure slave builds. https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/13900 https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-paladin/builds/25349
,
Mar 10 2017
it looks like the daisy-paladin already passed in https://uberchromegw.corp.google.com/i/chromeos/builders/daisy-paladin/builds/25348 not sure why it's triggered again.
,
Mar 10 2017
,
Mar 14 2018
This bug is Untriaged and very old. Because it has an owner, the status will be set to assigned to avoid closing a bug someone is using. If this bug still needs triage, change it back to Untriaged.
,
May 17 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by nxia@chromium.org
, Mar 10 2017