| Issue 3237: | Force pushed change is not set to merged | |
| 1 person starred this issue and may be notified of changes. | Back to list |
***************************************************************** ***** ***** ***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!! ***** ***** ***** ***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD, ***** ***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.***** ***** ***** ***** THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS ***** ***** ***** ***************************************************************** Affected Version: 2.11-rc0 What steps will reproduce the problem? 1. Upload a change for review by pushing to refs/for/master 2. Push the same change (or a rebased version) directly 3. What is the expected output? What do you see instead? Expected result is that the existing change is set to merged. If it was rebased, a new patch set is created before being set to merged. Actual result: the change remains open Please provide any additional information below. I've seen this on our live server running 2.11-rc0 but could not reproduce it on my development environment.
Apr 8, 2015
Project Member
#1
david.pu...@sonymobile.com
Apr 8, 2015
Seems to have been caused by the same NPE that was fixed in [1] https://gerrit-review.googlesource.com/#/c/65200/
Apr 8, 2015
Test added in: https://gerrit-review.googlesource.com/#/c/66932/
Status:
ChangeUnderReview
Apr 8, 2015
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.11
Apr 16, 2015
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |