Workaround: 'git cl issue <number>', e.g. for the above, I did 'git cl  issue 46306 '.

Moved issue gerrit:7214 to now be  issue chromium:764848 .

I reproduced this in chromium repo as well:

remote: Processing changes: new: 1, done            
remote: 
remote: New Changes:        
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/665662 Test        
remote: 
To https://chromium.googlesource.com/chromium/src.git
 * [new branch]                b88f84919b30ab4e58fc7384033375be7fe13b6b -> refs/for/refs/heads/master%wip,m=Initial_upload

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

Created|Updated 0 issues on Gerrit, but only 1 expected.

Seeing the same thing trying to land VERSION bump changes in src.git, which is preventing cutting a new Chrome build. Raising priority.

Yep, definitely an issue, and a change on the Gerrit side (since there aren't any git-cl or gerrit_util changes in depot_tools in the last few days). I just ran into it myself while uploading https://crrev.com/i/454272.

The remote now includes the project path in the "New Changes" block, so our output parsing is failing.

Old:
remote: New Changes:        
remote:   https://chromium-review.googlesource.com/XXXX Description goes here


New:

remote: New Changes:        
remote:   https://chromium-review.googlesource.com/#/c/chromium/src/+/XXXX Description goes here 


Fixing on the git-cl side.

This is blocking M61 Stable RC cut for Desktop.

https://chromium-review.googlesource.com/#/c/chromium/tools/depot_tools/+/665998

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/depot_tools/+/289b43183e98bdec9e8bc45be1eb462876cccebc

commit 289b43183e98bdec9e8bc45be1eb462876cccebc
Author: Aaron Gable <agable@chromium.org>
Date: Wed Sep 13 21:21:38 2017

git-cl: Parse new change urls containing project paths

Bug:  764848 
Change-Id: I639451ad54eb50a405fe44b9a83b00d84ec76578
Reviewed-on: https://chromium-review.googlesource.com/665998
Reviewed-by: Sergey Berezin <sergeyberezin@chromium.org>
Commit-Queue: Aaron Gable <agable@chromium.org>

[modify] https://crrev.com/289b43183e98bdec9e8bc45be1eb462876cccebc/tests/git_cl_test.py
[modify] https://crrev.com/289b43183e98bdec9e8bc45be1eb462876cccebc/git_cl.py

Should be fixed now. Please verify.

Oh no, catch-22. It looks like this problem has also been causing the recipe-roller to fail since:

https://uberchromegw.corp.google.com/i/internal.infra.cron/builders/recipe-autoroller-internal/builds/69022

but I guess it can't roll itself to the fi (or something), so is still failing, and so anything using depot_tools in recipes is also still broken (like the release bots).

Oh, but it still created the CLs - e.g. https://chromium-review.googlesource.com/c/infra/infra/+/665658
which I'm guessing we can just land manually?

LMK if I can be of help here (trooper).

Ah, good catch. I'll try to land them and see if that helps it get to the fix.

wpt-import (yet another roller) is also currently broken by this issue: https://build.chromium.org/p/chromium.infra.cron/builders/wpt-importer

I'm clearly still missing something here. I committed the pending roll CLs, in a few different repos, and the recipe roller appears to be back to the state it was in before (failing the skia step, but that has been happening for a long time), but depot_tools is still stuck at a revision from earlier today, 3 or 4 commits before this fix. Is there something else that controls the depot_tool rolls?

reassigning to recipe roller owners

The roll you committed (https://chromium-review.googlesource.com/c/infra/infra/+/665744) only updated the build pin, not the depot_tools pin. It needs a manual roll.

Yeah, I knew it didn't update depot_tools, but I thought after that got in, then it would create another one to update depot_tools. Or is depot_tools always rolled manually (which might be the something I'm missing)?

https://chromium-review.googlesource.com/c/chromium/tools/build/+/666081

not all changes to depot_tools (in particular, ones that don't touch recipes, like git-cl changes) don't trigger recipe rolls.

Ah, yeah, that makes sense, thanks.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/2b71719f0909acdd6443f1ff90c8d8ad5a692dd7

commit 2b71719f0909acdd6443f1ff90c8d8ad5a692dd7
Author: Aaron Gable <agable@chromium.org>
Date: Wed Sep 13 23:23:36 2017

Manually roll depot_tools recipes to pick up git-cl fix

TBR=nodir@chromium.org

Bug:  764848 
Change-Id: Ifa5e50a935a88ed9d1c866270486ce8668827633
Reviewed-on: https://chromium-review.googlesource.com/666081
Commit-Queue: Aaron Gable <agable@chromium.org>
Reviewed-by: Michael Moss <mmoss@chromium.org>

[modify] https://crrev.com/2b71719f0909acdd6443f1ff90c8d8ad5a692dd7/scripts/slave/README.recipes.md
[modify] https://crrev.com/2b71719f0909acdd6443f1ff90c8d8ad5a692dd7/infra/config/recipes.cfg

Manual roll landed; should result in cascading rolls into infra and other repos now.

Kicked this roll (https://chromium-review.googlesource.com/c/infra/infra/+/665838) and hopefully things will improve.

Recipe roller has started successfully uploading and landing its own changes in further downstream repos. This indicates that the roll into infra was sufficient to fix the issue for recipe roller, and should fix it for other bots as well.

Please verify.

Release bots look happy now. Thanks!

[Auto-generated comment by a script] We noticed that this issue is targeted for M-61; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-61 label, otherwise remove Merge-TBD label. Thanks.

 Issue 765035  has been merged into this issue.

 Issue gerrit:7024  has been merged into this issue.

 Issue 765154  has been merged into this issue.

 Issue 765325  has been merged into this issue.

 Issue 765259  has been merged into this issue.

 Issue 765314  has been merged into this issue.

FYI -- if you're still hitting upload failures, run "gclient" with no other args to pick up the fix, which is in git-cl itself.

Afterwards you'll need to re-upload any failing patch sets.

 Issue gerrit:7352  has been merged into this issue.

 Issue 772681  has been merged into this issue.

 Issue 766202  has been merged into this issue.

 Issue 765423  has been merged into this issue.