have a progress-aware-timeout to fail doomed hwtest runs faster |
|||||
Issue descriptionExample run: https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/16328 reef-paladin (and reef-uni) failed provision across the board: https://luci-milo.appspot.com/buildbot/chromeos/reef-paladin/3700 https://viceroy.corp.google.com/chromeos/suite_details?job_id=143582919 We spent 2 hours waiting for hwtest results from this, and didn't get a single result due to provision failing everywhere. A simple 60 minutes to first result timeout could have easily saved an hour from the CQ run. A more robust X minutes until Y results might be possible which would help even in cases where some provision jobs succeed but the run itself is still doomed to timeout.
,
Sep 21 2017
,
Sep 25 2017
,
May 10 2018
,
May 11 2018
This sounds like it sounds be considered for Torch |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by davidri...@chromium.org
, Sep 20 2017