New issue
Advanced search Search tips

Issue 851689 link

Starred by 1 user

Issue metadata

Status: Closed
Owner: ----
Closed: Jan 14
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Previous locations:
gerrit:9232


Sign in to add a comment

"git cl upload -d" claims to fail because patch already uploaded (not true) but it did half the work

Project Member Reported by brat...@opera.com, Jun 11 2018

Issue description

I tried to upload a CL with git cl upload -d, and after a long delay (half a minute? more?) I got an error back: Failed to create a change. The more detailed error message was commit(s) already exists (as current patchset)).

It looks like it did create a CL, but it did not start try runs. The CL in question was https://chromium-review.googlesource.com/c/chromium/src/+/1095336 (I started trybots manually).

Full input and output below:

bratell@bratell-linux:~/src/chromium/src/chrome/browser$ git cl upload -d
Running presubmit upload checks ...

Presubmit checks took 1.6s to calculate.

Presubmit checks passed.
 third_party/blink/renderer/core/frame/performance_monitor_test.cc |  8 ++++----
 third_party/blink/renderer/core/loader/idleness_detector_test.cc  | 12 ++++--------
 2 files changed, 8 insertions(+), 12 deletions(-)

remote: Processing changes: refs: 1, done            
remote: (W) 17ef5e5: commit subject >50 characters; use shorter first paragraph        
To https://chromium.googlesource.com/chromium/src.git
 ! [remote rejected] 17ef5e5ec9c0a114d96fd263ed9ccb364f6d850a -> refs/for/refs/heads/master%wip,m=Initial_upload (commit(s) already exists (as current patchset))
error: failed to push some refs to 'https://chromium.googlesource.com/chromium/src.git'

Error after CL description prompt -- saving description to /home/bratell/.git_cl_description_backup

Failed to create a change. Please examine output above for the reason of the failure.
Hint: run command below to diagnose common Git/Gerrit credential problems:
  git cl creds-check


 

Comment 1 by kaspern@google.com, Jun 11 2018

Project: chromium
Moved issue gerrit:9232 to now be  issue chromium:851689 .

Comment 2 by mar...@chromium.org, Jun 20 2018

Components: Infra>SDK
Labels: Pri-3 Type-Bug
Status: Untriaged (was: New)
Issue moved from a project with a different set of status labels. "New" is not a supported status in /p/chromium, so these ended up in a black-hole.
Status: Closed (was: Untriaged)
We've substantially re-written how git cl upload works since this bug was filed to address other upload issues. Given that there haven't been further reports of this issue I'm going to assume it was either transient or fixed. Please re-open if you're still having issues.

Sign in to add a comment