New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 765259 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 764848
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Two attempts to upload CL to gerrit failed with "Error after CL description prompt"

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

Issue description

Two attempts to upload a CL to gerrit failed with "Error after CL description prompt".  The CL was created on gerrit, but the link between that CL and my checkout doesn't exist ("git cl try" says to upload first).  

The CL created from the first attempt was https://chromium-review.googlesource.com/c/chromium/src/+/665586, which I abandoned to create a new one.  The second CL created is https://chromium-review.googlesource.com/#/c/chromium/src/+/666997.

The output from git cl upload and git cl try from the most recent attempt follows; let me know what debugging information you'd like from the checkout.

rdsmith-macbookpro:../chrome/src [CookieCallbacks] $ git cl format && git commit -m "git cl format" . && git cl upload
git cl format && git commit -m "git cl format" . && git cl upload
[CookieCallbacks d3b65a549094] git cl format
 1 file changed, 1 insertion(+), 1 deletion(-)
Running presubmit upload checks ...

Presubmit checks took 3.1s to calculate.

Presubmit checks passed.
 net/cookies/cookie_monster.cc | 27 +++++++++++++++++++++++----
 net/cookies/cookie_store.h    |  6 +++++-
 2 files changed, 28 insertions(+), 5 deletions(-)
Waiting for Emacs...
remote: Processing changes: new: 1, done            
remote: (W) 00c2d17: commit subject >50 characters; use shorter first paragraph        
remote: 
remote: New Changes:        
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/666997 Switch the subscription for cookie callbacks over to being opaque, and use ...        
remote: 
To https://chromium.googlesource.com/chromium/src.git
 * [new branch]                00c2d175cd1dbd990c0bdc322c199720f75b2035 -> refs/for/refs/heads/master%wip,m=Initial_upload

Error after CL description prompt -- saving description to /Users/rdsmith/.git_cl_description_backup

Created|Updated 0 issues on Gerrit, but only 1 expected.
Change-Id: Ieb61eab7518a5d428be556329fb296c0f162363a
rdsmith-macbookpro:../chrome/src [CookieCallbacks] $ git cl try
git cl try
Usage: git cl try [options]

git cl: error: Need to upload first
rdsmith-macbookpro:../chrome/src [CookieCallbacks] $ 
 

Comment 1 by kbr@chromium.org, Sep 15 2017

Cc: kbr@chromium.org aga...@chromium.org dgn@chromium.org tandrii@chromium.org
Labels: -Type-Bug -Pri-2 Pri-1 Type-Bug-Regression
See also  Issue 765314 . Upgrading to P1 because multiple users (myself included) are seeing the "Error after CL description prompt" and "Created|Updated 0 issues on Gerrit, but only 1 expected". In my case the CLs were updated successfully. If it's not a real error then it should be either a warning, or silenced.

Comment 2 by kbr@chromium.org, Sep 15 2017

Here's the output from my case:

Title for patchset [Not for commit: Remove LatencyInfo::sequence_number.]: 
remote: Processing changes: updated: 1, done            
remote: (W) 035ccfd: commit subject >50 characters; use shorter first paragraph        
remote: 
remote: Updated Changes:        
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/642517 Not for commit: Remove LatencyInfo::sequence_number.        
remote: 
To https://chromium.googlesource.com/chromium/src.git
 * [new branch]                035ccfd28b9db0d3d63497ea89b2e37745d05eb6 -> refs/for/refs/heads/master%notify=NONE,m=Not_for_commit_Remove_LatencyInfosequence_number

Error after CL description prompt -- saving description to /Users/kbr/.git_cl_description_backup

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

Update depot_tools. Aaron has actally added a fix to depot_tools in advance of this release, but your depot_tools is out of date.

Comment 4 by kbr@chromium.org, Sep 15 2017

OK. I'm not sure why it wouldn't have been updated before, but it seems to be at HEAD right now.

Comment 5 by aga...@chromium.org, Sep 15 2017

Mergedinto: 764848
Status: Duplicate (was: Untriaged)

Sign in to add a comment