| 2025-10-09 20:34:09 |
147508 |
@bors retry |
| 2025-10-09 07:44:10 |
146568 |
Yielding to enclosing rollup.
@bors retry (yield) |
| 2025-10-09 03:12:57 |
147492 |
@bors retry |
| 2025-10-07 20:35:21 |
147423 |
@bors retry |
| 2025-10-07 12:47:45 |
145608 |
Yielding to overarching rollup @bors retry |
| 2025-10-07 12:46:47 |
147440 |
Killed. Spurious.
@bors retry |
| 2025-10-07 11:44:51 |
145608 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-06 09:06:15 |
147392 |
@bors retry |
| 2025-10-05 06:00:11 |
147284 |
> collect2: fatal error: ld terminated with signal 7 [Bus error], core dumped
Hm, maybe spurious?
@bors retry |
| 2025-10-05 04:35:43 |
147310 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-04 22:40:45 |
147284 |
@bors retry |
| 2025-10-04 06:05:25 |
147308 |
@bors retry |
| 2025-10-04 02:54:49 |
147284 |
@bors retry |
| 2025-10-03 21:14:40 |
147284 |
Hmm, I don't see any CI changes on master for that kind of error -- maybe it was spurious?
@bors retry |
| 2025-10-03 09:02:02 |
142771 |
@bors retry (spurious network error) |
| 2025-10-02 22:55:39 |
146166 |
Looking at the rich GHA logs of the failed job `auto dist-x86_64-msvc-alt`,
I see an abrupt end at line 10655 simply containing ` Compiling rustc-main v0.0.0 (D:\a\rust\rust\compiler\rustc)`, I can't scroll further down; when I scroll back up, I can only go til line 9661; nothing suspicious except some C++ compiler warnings.
I tried to *view the raw logs* but that failed with *Failed to generate URL to download logs.*; I tried to *download log archive* but the download failed after several MBs transmitted.
This gotta be spurious!
@bors retry |
| 2025-10-01 18:16:43 |
147210 |
@bors retry |
| 2025-10-01 12:31:20 |
142771 |
> Canceling since a higher priority waiting request for CI-refs/heads/auto exists
@bors retry |
| 2025-10-01 11:26:55 |
147210 |
@bors retry bad day for MacOS? |
| 2025-10-01 04:45:09 |
147198 |
@bors retry |
| 2025-09-29 00:51:55 |
147090 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-27 09:35:58 |
147030 |
@bors retry (runner flaked out) |
| 2025-09-27 00:43:42 |
147074 |
@bors retry dist-x86_64-linux stuck after 5 hours |
| 2025-09-27 00:34:06 |
146355 |
@bors retry |
| 2025-09-25 14:16:02 |
146697 |
@bors retry (flaky) |
| 2025-09-25 07:23:56 |
146981 |
@bors retry |
| 2025-09-25 05:10:48 |
146981 |
@bors retry |
| 2025-09-25 03:38:08 |
146981 |
Still looks spurious but doesn't look like the same failure.
@bors retry |
| 2025-09-25 03:08:37 |
147003 |
@bors retry |
| 2025-09-25 00:31:36 |
146981 |
For after things get fixed,
@bors retry |
| 2025-09-24 09:54:15 |
146946 |
@bors retry |
| 2025-09-24 04:35:26 |
146946 |
@bors retry |
| 2025-09-23 18:13:05 |
146931 |
@bors retry |
| 2025-09-23 17:59:42 |
146931 |
@bors retry all the runners are aborted bc of github outage |
| 2025-09-22 10:24:22 |
145411 |
@bors retry (flaky) |
| 2025-09-22 09:47:11 |
146683 |
@bors retry curl: (35) Recv failure: Connection was reset |
| 2025-09-22 06:33:17 |
145411 |
@bors retry |
| 2025-09-22 06:32:52 |
146876 |
@bors retry (flaky) |
| 2025-09-22 06:15:03 |
145411 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-22 05:02:54 |
145411 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-22 04:12:15 |
145411 |
One of the jobs is stuck in a “queued” state with no runner, and will never complete.
@bors retry |
| 2025-09-21 21:28:33 |
145411 |
seems spurious, a codegen test can't make a rustc build fail.
@bors retry |
| 2025-09-21 04:44:05 |
144091 |
Yielding to rollup again. Sorry for the noise; CI has been flaking out.
@bors retry |
| 2025-09-21 00:35:29 |
144091 |
@bors retry same thing |
| 2025-09-21 00:35:05 |
146825 |
@bors retry timeout in rustdoc tests |
| 2025-09-20 23:09:12 |
144091 |
@bors retry rolled up |
| 2025-09-20 17:23:44 |
146744 |
@bors retry |
| 2025-09-20 16:34:42 |
146793 |
@bors retry |
| 2025-09-20 08:02:05 |
146771 |
@bors retry curl: (28) Operation too slow. Less than 10 bytes/sec transferred the last 30 seconds |
| 2025-09-19 20:54:45 |
146740 |
@bors retry r- |
| 2025-09-19 07:34:11 |
146687 |
One of the jobs flaked out and stopped making progress, hours ago. 😿
@bors retry |
| 2025-09-18 08:35:55 |
146434 |
@bors retry |
| 2025-09-16 09:43:07 |
146259 |
@bors retry (flaked out) |
| 2025-09-16 07:44:47 |
143613 |
Yielding to enclosing rollup.
@bors retry |
| 2025-09-16 04:25:13 |
146402 |
Yield to enclosing rollup, which failed due to a GitHub runner flaking out.
@bors retry |
| 2025-09-16 04:24:32 |
146614 |
@bors retry (runner flaked out) |
| 2025-09-15 12:41:16 |
146344 |
@bors retry |
| 2025-09-15 12:29:57 |
146575 |
Flaky, but a different test.
@bors retry |
| 2025-09-15 12:29:37 |
146582 |
Suspected flaky rustdoc-gui test.
@bors retry |
| 2025-09-15 11:09:30 |
146575 |
Flaky failure in #146582; yielding again.
@bors retry |
| 2025-09-15 11:04:09 |
146582 |
@bors retry |
| 2025-09-15 10:53:31 |
146575 |
Yielding for beta (well, to resolve a beta blocker)
@bors retry |
| 2025-09-15 04:36:28 |
146545 |
Host runner lost
@bors retry |
| 2025-09-14 20:01:01 |
146402 |
@bors retry |
| 2025-09-14 18:40:55 |
146545 |
@bors r- retry |
| 2025-09-14 10:17:40 |
145881 |
@bors retry |
| 2025-09-13 22:49:16 |
146507 |
thread 'package::reserved_windows_name' (1900) panicked at src\tools\cargo\
Hopefully spurious? @bors retry |
| 2025-09-13 04:34:02 |
145471 |
@bors retry |
| 2025-09-12 04:25:23 |
146019 |
Looks spurious?
@bors retry |
| 2025-09-12 02:52:54 |
144549 |
@bors retry |
| 2025-09-11 12:58:56 |
145177 |
That was a spurious failure...
@bors retry |
| 2025-09-11 07:05:26 |
146429 |
@bors retry (runner flaked out) |
| 2025-09-11 04:27:21 |
146400 |
@bors retry (runner flaked out again) |
| 2025-09-10 21:40:51 |
146400 |
@bors retry |
| 2025-09-10 15:30:53 |
146350 |
@bors retry |
| 2025-09-10 15:11:14 |
146400 |
@bors retry network error |
| 2025-09-10 15:00:37 |
146409 |
@bors retry |
| 2025-09-10 01:49:49 |
146324 |
Bors, this was already merged.
@bors r- retry |
| 2025-09-09 11:53:38 |
146360 |
One of the runners has been stuck for hours for no reason. 😿
@bors retry |
| 2025-09-08 13:33:10 |
146111 |
timeout
@bors retry |
| 2025-09-08 02:58:32 |
146199 |
This PR is pending but it's already merged?
@bors retry |
| 2025-09-08 02:58:18 |
146257 |
This PR is pending but it's already merged?
@bors retry |
| 2025-09-06 00:10:42 |
146199 |
@bors retry rolled up |
| 2025-09-05 20:48:06 |
146244 |
Kick out of queue.
@bors retry |
| 2025-09-05 17:48:59 |
146244 |
@bors retry |
| 2025-09-05 13:16:52 |
145690 |
Bors, please, it's already merged.
@bors r- retry |
| 2025-09-05 13:15:45 |
144342 |
Hey bors this has already merged.
@bors r- retry |
| 2025-09-03 07:16:05 |
146141 |
@bors retry |
| 2025-09-03 01:56:47 |
145279 |
@bors retry
Put in a rollup |
| 2025-09-02 09:59:16 |
146107 |
@bors retry |
| 2025-09-01 08:15:30 |
145961 |
@bors retry |
| 2025-08-30 23:50:22 |
146030 |
Put this in a rollup,
@bors retry |
| 2025-08-30 01:09:28 |
144494 |
"The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error."
@bors retry |
| 2025-08-29 20:55:44 |
145756 |
@bors retry |
| 2025-08-29 19:55:52 |
142390 |
@bors retry |
| 2025-08-29 17:02:51 |
142390 |
@bors retry |
| 2025-08-29 13:35:25 |
145997 |
@bors retry
|
| 2025-08-28 20:49:05 |
145947 |
"error: the evaluated program deadlocked" seems unrelated to this PR.
@bors retry |