git drover crashes when running in parallel |
||||||||
Issue descriptionI was git drover'ing a CL and while waiting for gnumbd to do it's thing, I started a second git drover which also ended up waiting for gnumbd. Once the first one landed, however, the second one crashed: first git drover: ----------------- Fetching pending ref refs/pending/branch-heads/2704... Cherry-picking commit on top of pending ref... Pushing commit to refs/pending/branch-heads/2704... It can take a while. Commit pushed to pending ref successfully! Waiting for commit to be landed on refs/branch-heads/2704... (If you are impatient, you may Ctrl-C once without harm) Found commit on refs/branch-heads/2704 Closing issue (you may be prompted for your codereview password)... second git drover ----------------- Fetching pending ref refs/pending/branch-heads/2704... Cherry-picking commit on top of pending ref... Pushing commit to refs/pending/branch-heads/2704... It can take a while. Commit pushed to pending ref successfully! Waiting for commit to be landed on refs/branch-heads/2704... (If you are impatient, you may Ctrl-C once without harm) Error: Command 'cl land --bypass-hooks' failed: Command '['git', 'cl', 'land', '--bypass-hooks']' returned non-zero exit status 1
,
Apr 25 2016
Robbie, do you think this is git-drover killing other git processes, or is it git cl land being confused?
,
Apr 25 2016
Is this 2 drovers in the same working directory? I didn't actually write git-drover though, so I dunno if it does any anti-parallel stuff :/. It kinda looks like git-cl-land though.
,
Apr 27 2016
,
Apr 27 2016
it's the same checkout, but I thought git drover creates it's own working directory?
,
Apr 27 2016
It's possible that git-drover actually manipulates refs in the .git folder, which could cause conflicts... I'm not sure though. I'm moving this over to Infra>SDK for further triage.
,
Aug 2 2016
,
Sep 1 2016
,
Sep 4 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
The gerrit git drover now does no work locally -- it just makes API calls to Gerrit. This should no longer be a problem. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by jochen@chromium.org
, Apr 25 2016