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

Issue 795863 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Pre-CQ bugs out with "No configuration target found for reef-uni-no-vmtest-pre-cq"

Project Member Reported by ejcaruso@chromium.org, Dec 18 2017

Issue description

e.g. https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/769300

The pre-CQ keeps sort-of-rejecting this change and others in the topic with the following message:

"No configuration target found for reef-uni-no-vmtest-pre-cq.
You can check the available configs by running `cbuildbot --list --all`.
The config may have been changed or removed, you can try to rebase your CL so it can get re-screened by the Pre-cq-launcher."

However, this target was removed on Nov 18, and this and related CLs have been rebased several times since then to no avail. I say sort-of-rejecting because it looks like the pre-cq does pick up the change regardless, but the CQ bit is nonetheless reset to 0 automatically, which means these changes won't go into the CQ.
 

Comment 1 by nxia@chromium.org, Jan 9 2018

Mergedinto: 737674
Status: Duplicate (was: Assigned)
it's because the CL was created before the config was removed, and Pre-CQ-Launcher isn't able to update the Pre-CQ configs to run accordingly for now. 

One way to work around this is to upload a new patch-set, simply updating the commit message can also work.

Sign in to add a comment