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

Issue 753879 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Feature



Sign in to add a comment

Distinguish provision failure from lab_only_failure

Project Member Reported by nxia@chromium.org, Aug 9 2017

Issue description

 issue 753838  - A bad CL caused provision failures on slaves, and the failures were treated as lab_only_failure and so no CLs were rejected. CQ kept picking up all CLs including the bad CL to retry and the CQ kept failing. Probably need a better mechanism to distinguish provision failures from other lab failures, so the master can kick out potential bad CLs. 

jrbarnette@ suggested the run_suite job can return a different code for provision failures.

http://shortn/_b6Z7iLgSmd
 
Cc: davidri...@chromium.org snanda@chromium.org
Labels: -Type-Bug -Pri-2 Pri-1 Type-Feature
This is potentially a high impact change, but with some risk too.

Will bring it up for discussion at cq taskforce.

Comment 2 by nxia@chromium.org, Jun 8 2018

Cc: -nxia@chromium.org

Sign in to add a comment