New issue
Advanced search Search tips

Issue 765319 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Can't upload dependent patch, keep getting "Upload upstream branch <foo> first", even after re-uploading upstream branch.

Project Member Reported by mattm@chromium.org, Sep 14 2017

Issue description

What steps will reproduce the problem?
1. Uploaded https://chromium-review.googlesource.com/c/chromium/src/+/665261
2. Uploaded dependent patch https://chromium-review.googlesource.com/c/chromium/src/+/665986
3. Updated 665261
4. rebased (git rebase-update)
5. Uploaded rebase to 665261
6. Tried to upload rebase to 665986, but got "Upload upstream branch extract-generalnames first." error.
7. Abonded 665986.
8. ran git cl issue 0.
9. Tried to upload new dependent patchset, still get "Upload upstream branch extract-generalnames first." error.
10. Uploaded another patchset to 665261 just to be sure I really uploaded the rebase.
11. repeat step 9

What is the expected output?
git cl upload for dependent patchset works.

What do you see instead?
Upload upstream branch extract-generalnames first.
It is likely that this branch has been rebased since its last upload, so you just need to upload it again.
(If you uploaded it with --no-squash, then branch dependencies are not supported, and you should reupload with --squash.)


 

Comment 1 by sortie@google.com, Sep 14 2017

Cc: sortie@google.com
Status: WontFix (was: Unconfirmed)
Unfortunately I can't help here; I expect that something was messed up locally (like a typo in branch names) but without the output of "git map-branches -vvv" I can't help, and I'm sure these branches are long gone.

Sign in to add a comment