New issue
Advanced search Search tips

Issue 902505 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Feature

Blocking:
issue 902504
issue 902513


Show other hotlists

Hotlists containing this issue:
CrOSParallelCQ


Sign in to add a comment

Land changes to CQ launcher to identify the difference between CQ +1 and +2

Project Member Reported by jclinton@chromium.org, Nov 6

Issue description

Potentially, the CQ launcher will be running a sandbox environment or—at least—partially ready to go but not yet running the CQ. This feature should be flag-controlled so that it can work with the old and new behavior. During the transition:

* Flag off means old behavior: Tryjob-Ready +1 runs PCQ without hardware testing and without submit. CQ +1 is full run to submission with hardware testing.

* Flag on means new behavior: CQ +1 runs PCQ without hardware testing and without submit. CQ +2 is full run to submission with hardware testing.

 
Blocking: 902513
Labels: Disable-Nags

Sign in to add a comment