New issue
Advanced search Search tips

Issue 633631 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 600469



Sign in to add a comment

It’s not obvious how to turn a CQ dry run into a wet one

Project Member Reported by mark@chromium.org, Aug 2 2016

Issue description

For Chromium, “git cl try” now launches a CQ dry run.

On Rietveld, it’s not clear how to turn a CQ dry run that’s in progress into a wet one. It seems like we’re expected to uncheck the CQ box and then re-check it. This isn’t obvious. It’s not clear to the would-be unchecker that this will use the existing green (or in-progress yellow) bots and not start all bots over again from scratch.

Why would you want to do this? Maybe all of the interesting bots that you care about have already gone green, you have LGTM, and you don’t want to wait around for the rest of the bots in the dry run to turn green before sending it to the wet CQ.
 
Components: -Infra Infra>CQ
Blockedon: 600469
Status: Available (was: Untriaged)
We are aware of this, but we are focusing on Gerrit, which has this problem fixed. Rietveld is deprecated, though if send us a patch, we'll deploy it.
Also, "git cl set-commit" is cmd alternative.
 Issue 655741  has been merged into this issue.
Components: Infra>Codereview>Rietveld
Status: WontFix (was: Available)
Closing in bulk due to Rietveld’s deprecation in favor of Gerrit. If you feel this bug should not have been closed, please feel free to re-open.

Sign in to add a comment