New issue
Advanced search Search tips

Issue 845430 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

git cl upload outcome is "Created|Updated 2 issues on Gerrit, but only 1 expected."; Can't submit CL

Project Member Reported by awdf@chromium.org, May 22 2018

Issue description

What steps will reproduce the problem?
(1) Attempt to upload this patch https://chromium-review.googlesource.com/c/chromium/src/+/1065995 via git cl upload

What is the expected result?
One CL created


What happens instead?
 chrome/browser/notifications/notification_interactive_uitest.cc | 30 ------------------------------
 1 file changed, 30 deletions(-)          
remote: Processing changes: new: 2, done
remote: (W) 058fb22: commit subject >50 characters; use shorter first paragraph
remote:                                                   
remote: New Changes:
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/1068728 FREEZE.unindexed [WIP]
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/1068729 [Tests] Delete NotificationsTest.TestOri
ginPrefsNotSavedInIncognito [WIP]
remote:
To https://chromium.googlesource.com/chromium/src.git
 * [new branch]                058fb2247c888e1061dfa6f4ae2e2bb74a95ce4a -> refs/for/refs/heads/master%wip,m=Initial_up
load,hashtag=tests

Error after CL description prompt -- saving description to /usr/local/google/home/awdf/.git_cl_description_backup

Created|Updated 2 issues on Gerrit, but only 1 expected.
Change-Id: I91ea55c37ba7d6af4598a7b7f174c4e54ad092b2


I tried deleting the erroneously created CL but it still won't let me submit the actual CL because it still depends on it; I don't know how to get rid of the dependency.

Tried again via `git cl upload 0` to unlink and re-uploading but got exactly the same result.
 

Comment 1 by awdf@chromium.org, May 29 2018

Status: WontFix (was: Untriaged)
Turns out I had a local commit on my local 'master' branch that I have no recollection of creating called 'FREEZE.unindexed'. Getting rid of this commit and rebasing fixed the issue.

Sign in to add a comment