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

Issue 710941 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 737674
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Old Pre-CQs were removed from Pre-CQ-Set but were still triggered on some CLs

Project Member Reported by nxia@chromium.org, Apr 12 2017

Issue description

caroline-pre-cq was removed from the default pre-cq set last week, but some CLs had already inserted CLAction entries with caraline-pre-cq into the CIDB.CLActionTable, and they were still scheduled to run caraline-pre-cq

The simple way to avoid this is to upload a new patch, but the infra needs a way to avoid that.


https://chromium-review.googlesource.com/c/468737/
 

Comment 1 by nxia@chromium.org, Jun 9 2017

Cc: akes...@chromium.org pprabhu@chromium.org
 Issue 731805  has been merged into this issue.

Comment 2 by nxia@chromium.org, Jun 9 2017

Labels: -Pri-3 Pri-2
Is this about us trying to launch trybots with the wrong config, or with configs that no longer exist?
The currently active symptom is configs that no longer exist.
Simplest fix would for for pre-cq-launcher to filter our configs that don't exist (according to its chromeos_config) from its launch logic and fully_verified detection logic.

Comment 6 by nxia@chromium.org, Jun 9 2017

some pre-cq configs are just moved out of the default set, not removed from the config list, so they still exist 

Comment 7 by nxia@chromium.org, Mar 19 2018

Mergedinto: 737674
Status: Duplicate (was: Untriaged)

Sign in to add a comment