Issue metadata
Sign in to add a comment
|
Multiple trybots report patch failure with "a cherry-pick or revert is already in progress" |
||||||||||||||||||||||
Issue descriptionIn this tryjob: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/fuchsia_arm64/71089 from this CL: https://chromium-review.googlesource.com/1131010 the fuchsia_arm64 bot reported patch application failure with: [0:01:43] Failed to apply 'https://chromium.googlesource.com/chromium/src.git' @ 'refs/changes/10/1131010/3' to 'ce49be89d27ecc9b15bd04cc1c87e11ae3d8d77b' at '/b/swarming/w/ir/cache/builder/src' [0:01:43] git returned non-zero exit status 128: error: a cherry-pick or revert is already in progress hint: try "git cherry-pick (--continue | --quit | --abort)" fatal: cherry-pick failed ---------------------------------------- src (ERROR) ---------------------------------------- This error message seems wrong even if the patch didn't apply. Could someone please take a look? Maybe this bot is just hosed and needs to be clobbered. Marking P1 because this is probably causing flakes on the CQ. https://chromium-swarm.appspot.com/bot?id=swarm617-c4&sort_stats=total%3Adesc
,
Jul 17
Happening on chromium_presubmit too: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromium_presubmit/171351 Raising to P0; has been happening just recently, no other filed bug, unclear whether it's known.
,
Jul 17
Looks like https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1139553, reverting.
,
Jul 17
Revert has made it into the recipe bundle.
,
Jul 17
chromium_presubmit appears to have recovered, e.g. https://chromium-swarm.appspot.com/bot?id=swarm893-c4 Waiting for more data on longer-running trybots, though I suspect this is fixed.
,
Jul 17
Marking as fixed.
,
Jul 17
,
Jul 17
Issue 864480 has been merged into this issue.
,
Jul 17
Issue 864473 has been merged into this issue.
,
Jul 18
Reopening rather than filing a new bug because this has started again: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel/36693 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel/36691
,
Jul 18
,
Jul 19
I tried a couple of led runs on the same bot where https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel/36691 failed and things seem to work fine... https://chromium-swarm.appspot.com/task?id=3ec8c0166c4c1710&refresh=10 https://chromium-swarm.appspot.com/task?id=3ec8c62a81117310&refresh=10 <intentional-failure> https://chromium-swarm.appspot.com/task?id=3ec8c8cc16dd9f10&refresh=10 <ok again> I wonder if it's because the first time we landed this, the bot was left with a cherry-pick on progress, so it affected the first run of the reland (because we cancel cherry-picks in progress after we try to cherry-pick, not before). Maybe subsequent runs would have been fine?
,
Jul 19
Two builds - not consecutive - failed in this way on that bot while this CL was landed in depot_tools: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel/36693 https://ci.chromium.org/p/chromium/builders/luci.chromium.try/linux_chromium_headless_rel/36691
,
Jul 19
Sorry, I meant swarming bot. 36693 ran in swarm1813-c4 and 36693 ran in swarm1815-c4. The led tasks I ran were all on swarm1815-c4
,
Jul 19
*36691 ran in swarm1815-c4
,
Jul 19
linux_chromium_headless_rel looks good now. Reducing priority
,
Jul 19
the revert fixed the issue again. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kbr@chromium.org
, Jul 17