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

Issue 637164 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug

Blocking:
issue skia:5612



Sign in to add a comment

Reverts do not immediately land in PolyGerrit

Project Member Reported by martiniss@chromium.org, Aug 12 2016

Issue description

What steps will reproduce the problem?
1. Revert a change
2. CQ the change

What is the expected output?
The change will land

What do you see instead?
The change doesn't land

Please provide any additional information below.
See https://chromium-review.googlesource.com/c/368510 for example. TBR doesn't seem to be working :(
 
Cc: -tandrii@chromium.org
Labels: Proj-Gerrit-Migration
Owner: tandrii@chromium.org
Status: Assigned (was: Untriaged)
Cc: tandrii@chromium.org
Owner: rmis...@chromium.org
Ravi, isn't this something you've been working on? If not, re-assign back to me or mark untriaged.
FTR, the only thing missing right now is that REVERT buttong doesn't set self-LGTM on the change, that is  Code-Review+1 is missing.

Comment 4 by rmis...@google.com, Aug 12 2016

Cc: rmis...@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
No, not yet. But this is something that is obviously important to fix for reverts.

Leaving it untriaged in case somebody gets to it before me.
Labels: -Pri-2 Pri-1
Status: Available (was: Untriaged)
Thanks for speedy reply. Let's keep it available since it has clearly been triaged just now :) Also, this is Pri1.
Labels: Milestone-Fishfood
Owner: rmis...@chromium.org
Status: Assigned (was: Available)
Ravi, mark this as fixed if it is. I know you did work around this in the chromium gerrit plugin.

Comment 7 by rmis...@google.com, Sep 28 2016

Blocking: skia:5612

Comment 8 by rmis...@google.com, Sep 28 2016

Andy, any pointers on how to automatically set Code-Review+1 when a new revert issue is created?
You could make a request to the REST API to set the label via a plugin.
One other method would be to add the ability to Gerrit to set labels on the new change that will be created.

This would require adding a `labels` field to RevertInput, then using those to create a new change. https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#revert-input

I think this is the best way to go, actually.

Comment 11 by rmis...@google.com, Sep 29 2016

I have an approach I am working on that is slightly different and does not require an API change. But I think it will make adding labels to the revert call easy if 'labels' are added in the future to RevertInput. I will send it out for review later today and we can discuss there.

Comment 12 by rmis...@google.com, Sep 29 2016

Status: Started (was: Assigned)
Sent out for review https://gerrit-review.googlesource.com/c/87490

Comment 13 by rmis...@google.com, Sep 29 2016

Summary: Reverts do not immediately land in PolyGerrit (was: TBR doesn't work on gerrit )
Renaming issue
Status: Fixed (was: Started)
https://critique.corp.google.com/#review/134671402 has been submitted and the change is now live.

I did observe that sometimes after you hit revert you do not see the labels show up right away. The labels are applied and the change does get submitted, but the initial redirect to the issue does not show this because the /revisions/current/review REST API has a small lag.
This experience will be improved whenever gerrit:4671 is resolved. Andy, let me know if you have another way to solving this.

Marking this as fixed.

Sign in to add a comment