New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767119 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

have a progress-aware-timeout to fail doomed hwtest runs faster

Project Member Reported by akes...@chromium.org, Sep 20 2017

Issue description

Example 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.
 
Cc: davidjames@chromium.org
I think there's already a few other issues for timeouts for HWTests and provisions already.  Can we just include this one of those?

Comment 2 by xixuan@chromium.org, Sep 21 2017

Labels: Chase-Pending
Labels: -Chase-Pending
Cc: -davidjames@chromium.org
Owner: cra...@chromium.org
Status: Assigned (was: Untriaged)
This sounds like it sounds be considered for Torch

Sign in to add a comment