New issue
Advanced search Search tips

Issue 789103 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

error message when I can't git cl upload not helpful

Project Member Reported by jochen@chromium.org, Nov 28 2017

Issue description

when e.g. the commit bot decides to CQ-1 my CL while I upload a patch (which happened twice in the last hour), I get the following error on my terminal:

Running presubmit upload checks ...

Presubmit checks took 33.4s to calculate.

Presubmit checks passed.
 .../WebKit/Source/bindings/core/v8/custom/V8WindowCustom.cpp  | 11 +++++++++++
 third_party/WebKit/public/platform/web_feature.mojom          |  1 +
 tools/metrics/histograms/enums.xml                            |  1 +
 3 files changed, 13 insertions(+)
error: remote unpack failed: error Missing unknown b71e4fc98da03642b575bbbbf66dcf6cefb3a475
To https://chromium.googlesource.com/chromium/src.git
 ! [remote rejected]           89aa2862827098131f8ac35dd261e6a426b5f55b -> refs/for/refs/heads/master%notify=NONE,m=usecounter (n/a (unpacker error))
error: failed to push some refs to 'https://chromium.googlesource.com/chromium/src.git'

Error after CL description prompt -- saving description to /usr/local/google/home/eisinger/.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

Ideally, git cl wouldn't fail, but if it has to, at least it should tell me that there was a midair collision instead of suggesting that my credentials are broken
 
Status: WontFix (was: Untriaged)
The failure is that the commit object you're pushing has a reference to b71e4fc..., but the server does not have a reference to that object. As such, it fails to unpack the object you push.

The error message is there:
error: remote unpack failed: error Missing unknown b71e4fc98da03642b575bbbbf66dcf6cefb3a475
(unpacker error)

Anything more than that requires parsing stdout, which we don't want to be in the business of.

Sign in to add a comment