Issue metadata
Sign in to add a comment
|
edgar-paladin: Single provision job failure led to suite failure |
||||||||||||||||||||||||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromeos/edgar-paladin/1224 One provision failed due to mystery (no logs from repair because we had to do USB install, so no way we can find out why): https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/151996677-chromeos-test/chromeos4-row12-rack8-host15/ stuff happens! But we are supposed to be resillient to a single provision failure. This provision monopolized the test it was running for 40 minutes, and so the test was never retried, failing the suite. That is an infra bug with high impact -- uncontrollable low percentage of provision failures are leading to build failures.
,
Oct 27 2017
I've filed bugs in the past about inefficiencies in the DUT-fail-to-repair cycle. But I'm restricting this to just the time spent after provision fails, because that directly translates to a single provision failure leading to a build failure, which has high impact.
,
Oct 27 2017
Based on the description on this, sounds like it will be addressed by up-front-provision-suite.
,
Oct 30 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by pprabhu@chromium.org
, Oct 27 2017