multiple bots suffering patch failure |
|||||||
Issue descriptionit seems multiple bots are suffering from patch failure error is ===Running apply_issue.bat --root_dir src --issue 1853533002 --server https://codereview.chromium.org --force --ignore_deps -v -v --no-auth --patchset 40001 --whitelist DEPS (attempt #1)=== In directory: E:\b\build\slave\win\build Connecting to https://codereview.chromium.org DEBUG rietveld( 402): POSTing to /api/1853533002, args {'payload': None, 'timeout': 15}. DEBUG rietveld( 419): /api/1853533002 DEBUG rietveld( 402): POSTing to /1853533002/patchset/40001/get_depends_on_patchset, args {'timeout': 15, 'payload': '---M-A-G-I-C---B-O-U-N-D-A-R-Y-0---\r\n', 'content_type': 'multipart/form-data; boundary=-M-A-G-I-C---B-O-U-N-D-A-R-Y-0-'}. DEBUG rietveld( 419): /1853533002/patchset/40001/get_depends_on_patchset Request to https://codereview.chromium.org/1853533002/patchset/40001/get_depends_on_patchset failed: No patch set exists with that id (40001) Downloading patch from https://codereview.chromium.org/1853533002/#ps40001 DEBUG rietveld( 402): POSTing to /api/1853533002/40001, args {'payload': None, 'timeout': 15}. DEBUG rietveld( 419): /api/1853533002/40001 Request to https://codereview.chromium.org/api/1853533002/40001 failed: No patch set exists with that id (40001) Failed to fetch the patch for issue 1853533002, patchset 40001. Try visiting https://codereview.chromium.org/1853533002 ===Failed in 0.0 mins=== examples are easy to find but here are some links: https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191079 https://build.chromium.org/p/tryserver.chromium.win/builders/win10_chromium_x64_rel_ng/builds/4 https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191018 https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191016 Coudl be https://codereview.chromium.org/1852593002/ but this has already been reverted.
,
Apr 1 2016
,
Apr 1 2016
,
Apr 1 2016
Looks like there was a short string of bot_update failures due to connection issues to rietveld, but I'm not seeing that anymore. However, there are a suspicious number of patch_failures. Might actually be due to merge conflicts on a few CLs. I'll keep looking.
,
Apr 1 2016
All recent patch failures have been due to legitimate merge conflicts: https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191125/steps/bot_update/logs/patch%20error https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191132/steps/bot_update/logs/patch%20error https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191138/steps/bot_update/logs/patch%20error https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/191146/steps/bot_update/logs/patch%20error I'm thinking what we saw earlier was just some transient network flake. Will keep monitoring.
,
Apr 4 2016
We're currently seeing the usual rate of patch errors across the cq bots. From what I can tell, they're all legitimate merge conflicts. Looks like it was just some rietveld/network weirdness that we saw momentarily on Friday.
,
Apr 26 2016
,
Apr 27 2016
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by wfh@chromium.org
, Apr 1 2016