long bot_update step for chromium_presubmit build |
|||||
Issue descriptionhttps://ci.chromium.org/p/chromium/builders/luci.chromium.try/chromium_presubmit/259140 is the relevant build It has an 8 minute long bot_update step, which seems to be very abnormal. https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8932216705732867488/+/steps/bot_update/0/stdout#L1348_0 also is confusing; that doesn't look to me like something that would take a long time. Are the timestamps on the logdog stuff correct? Maybe I'm misinterpreting them? Not super urgent.
,
Dec 6
This is bad. I haven't seen this on other repos yet, but there are hour long presubmits, which should not happen at all.
,
Dec 6
I see this in logs: 13:10:13.559265 git.c:576 trace: exec: git-credential-luci get 13:10:13.559278 run-command.c:640 trace: run_command: git-credential-luci get 13:10:13.568020 trace.c:420 performance: 0.008936076 s: git command: git credential-luci get fatal: unable to access 'https://chromium.googlesource.com/a/chromium/src.git/': transfer closed with outstanding read data remaining 13:12:00.038552 trace.c:420 performance: 193.830692163 s: git command: /b/swarming/w/ir/cipd_bin_packages/bin/git fetch -v --progress origin '+refs/heads/*:refs/heads/*' [W git.go:283] Transient error string identified in STDERR: "fatal: unable to access 'https://chromium.googlesource.com/a/chromium/src.git/': transfer closed with outstanding read data remaining\n" [W git.go:294] Retrying after 34.171875s (rc=128): transient error string encountered 13:12:34.215998 exec_cmd.c:59 Determined executable path from procfs: /b/swarming/w/ir/cipd_bin_packages/bin/git 13:12:34.216101 exec_cmd.c:130 Determined executable path: /b/swarming/w/ir/cipd_bin_packages/bin 13:12:34.216409 git.c:344 trace: built-in: git fetch -v --progress origin '+refs/heads/*:refs/heads/*' 13:12:34.287848 run-command.c:640 trace: run_command: git-remote-https origin https://chromium.googlesource.com/a/chromium/src.git 13:12:34.289115 exec_cmd.c:114 Determined executable path from ENV: /b/swarming/w/ir/cipd_bin_packages/libexec/git-core 13:12:34.289254 exec_cmd.c:130 Determined executable path: /b/swarming/w/ir/cipd_bin_packages/libexec/git-core fatal: unable to access 'https://chromium.googlesource.com/a/chromium/src.git/': The requested URL returned error: 502 13:13:28.088309 trace.c:420 performance: 53.872144804 s: git command: /b/swarming/w/ir/cipd_bin_packages/bin/git fetch -v --progress origin '+refs/heads/*:refs/heads/*' [W git.go:283] Transient error string identified in STDERR: "fatal: unable to access 'https://chromium.googlesource.com/a/chromium/src.git/': The requested URL returned error: 502\n" [W git.go:294] Retrying after 51.2578125s (rc=128): transient error string encountered 13:14:19.351590 exec_cmd.c:59 Determined executable path from procfs: /b/swarming/w/ir/cipd_bin_packages/bin/git 13:14:19.351694 exec_cmd.c:130 Determined executable path: /b/swarming/w/ir/cipd_bin_packages/bin 13:14:19.352084 git.c:344 trace: built-in: git fetch -v --progress origin '+refs/heads/*:refs/heads/*' 13:14:19.423332 run-command.c:640 trace: run_command: git-remote-https origin https://chromium.googlesource.com/a/chromium/src.git 13:14:19.424704 exec_cmd.c:114 Determined executable path from ENV: /b/swarming/w/ir/cipd_bin_packages/libexec/git-core
,
Dec 6
,
Dec 6
,
Dec 6
Original issue is old. New issue is a general git outage, tracking this in bug 912711. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jyasskin@chromium.org
, Dec 6Labels: -Pri-3 Pri-1
Status: Untriaged (was: Unconfirmed)