| 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 |
| 2025-08-27 12:42:43 |
145909 |
@bors retry
https://github.com/rust-lang/rust/issues/145927, random failure on x86_64-pc-windows-gnu |
| 2025-08-27 07:26:47 |
140737 |
@bors retry |
| 2025-08-26 22:49:03 |
138736 |
@bors retry |
| 2025-08-26 12:14:44 |
145855 |
@bors retry spurious npm rate limit |
| 2025-08-26 12:14:34 |
145855 |
@bors retry (tidy) |
| 2025-08-26 08:26:59 |
143689 |
Yielding to enclosing rollup, which flaked out.
@bors retry |
| 2025-08-26 08:26:23 |
145871 |
@bors retry (502 Bad Gateway) |
| 2025-08-25 15:20:33 |
145711 |
@bors retry |
| 2025-08-25 10:35:35 |
145717 |
@bors retry |
| 2025-08-24 11:01:59 |
145384 |
@bors retry |
| 2025-08-24 07:11:31 |
144531 |
@bors r- retry |
| 2025-08-24 07:11:21 |
145554 |
@bors r- retry |
| 2025-08-24 07:11:08 |
145307 |
@bors r- retry |
| 2025-08-24 03:59:40 |
144531 |
@bors retry
yielding to rollup that includes this PR |
| 2025-08-24 02:48:50 |
144531 |
Yield to enclosing rollup.
@bors retry |
| 2025-08-22 05:46:06 |
145358 |
@bors retry spurious |
| 2025-08-22 01:07:36 |
145384 |
GitHub Actions had an incident last night (a different one), https://www.githubstatus.com/incidents/c7kq3ctclddp
@bors retry |
| 2025-08-21 01:34:47 |
145244 |
@bors retry |
| 2025-08-20 18:32:27 |
145658 |
@bors retry |
| 2025-08-20 16:10:25 |
144086 |
@bors retry |
| 2025-08-20 00:35:03 |
144086 |
@bors retry |
| 2025-08-19 11:35:45 |
138736 |
This has merge conflicts.
@bors r- retry |
| 2025-08-19 10:14:55 |
144252 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:14:41 |
142871 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:12:21 |
145584 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:11:22 |
145563 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:11:02 |
145432 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:10:54 |
145405 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:10:47 |
145243 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:10:16 |
145041 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:10:10 |
145013 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:10:00 |
144960 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:09:51 |
144804 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:09:42 |
142681 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:09:35 |
141744 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 10:09:15 |
140956 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 08:27:36 |
144567 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 08:27:04 |
144476 |
Bors hasn't noticed that this was merged.
@bors r- retry |
| 2025-08-19 04:26:44 |
145588 |
GitHub is once again refusing to show useful logs, so I'm going to assume that the GHA runners exploded again.
@bors retry |
| 2025-08-18 16:15:31 |
142487 |
@bors retry |
| 2025-08-18 10:32:55 |
145551 |
Given that this succeeded in the past, and that GitHub won't even let me see the failure logs, I think it's reasonable to assume yet more CI flakiness.
@bors retry |
| 2025-08-18 07:54:18 |
145478 |
Even if this job spontaneously becomes unstuck, it's still not going to finish in under 6 hours. Better to reroll the CI dice now.
@bors retry |
| 2025-08-18 00:49:42 |
145478 |
@bors retry
https://github.com/rust-lang/rust/runs/48262739268
didn't finish the job without any obvious errors
|
| 2025-08-17 23:49:28 |
145526 |
@bors retry (msvc timeout) |
| 2025-08-17 18:04:59 |
145478 |
https://github.com/rust-lang/cargo/pull/15851 should unblock loongarch64.
@bors retry |
| 2025-08-17 09:09:04 |
145521 |
@bors r- retry |
| 2025-08-17 05:47:08 |
138736 |
@bors retry |
| 2025-08-17 02:35:49 |
144476 |
Yield to rollup=never; I'll make a rollup including this PR soon enough.
@bors retry |
| 2025-08-16 17:03:38 |
145488 |
Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))
@bors retry |
| 2025-08-16 17:03:07 |
145396 |
Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))
@bors retry |
| 2025-08-16 17:02:37 |
138736 |
Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))
@bors retry |
| 2025-08-16 15:26:09 |
145396 |
Network o.O ... again! At least 3 PRs have failed due to network issues in the last <24 hours, might need to bring this to T-infra...
@bors retry |
| 2025-08-16 12:57:49 |
138736 |
@bors retry (flaky) |
| 2025-08-16 11:56:22 |
145396 |
spurious? submodule checkouts never terminated or had some other failure, can't see the full logs
@bors retry |
| 2025-08-16 10:50:52 |
145284 |
@bors retry (flaky download failure?) |
| 2025-08-15 13:54:16 |
142071 |
unrelated
@bors retry |
| 2025-08-14 05:33:00 |
145373 |
@bors retry (flaky) |
| 2025-08-12 20:38:49 |
145319 |
presumably that is spurious
@bors retry |
| 2025-08-12 12:50:34 |
145093 |
@bors retry Same reserved_windows_name failure also happened on https://github.com/rust-lang/rust/pull/145161 recently. |
| 2025-08-12 09:19:40 |
145093 |
@bors retry Not super clear what actually failed there, but it looks spurious. |
| 2025-08-12 06:45:51 |
145285 |
@bors retry (flaky?) |
| 2025-08-10 12:46:37 |
145210 |
Looks mega spurious.
@bors retry |
| 2025-08-10 05:43:45 |
145197 |
I think #144544 is failing?
@bors r- retry |
| 2025-08-09 18:10:24 |
145104 |
@bors retry |
| 2025-08-09 07:29:31 |
145142 |
> `client.read_exact(&mut header) failed with Connection reset by peer (os error 104)`
https://triage.rust-lang.org/gha-logs/rust-lang/rust/47726534304#2025-08-09T07:27:09.9986295Z
seems spurious?
@bors retry |
| 2025-08-08 20:53:37 |
144873 |
@bors retry |
| 2025-08-08 20:53:18 |
145086 |
@bors retry |
| 2025-08-08 20:53:15 |
143376 |
@bors retry |
| 2025-08-08 20:53:04 |
144787 |
@bors retry |
| 2025-08-08 16:46:04 |
144722 |
@bors retry float precision failure |
| 2025-08-07 07:39:58 |
143764 |
Yield to never PRs while we figure out why the rollup failed.
@bors retry |
| 2025-08-06 12:11:02 |
143679 |
Yielding to enclosing rollup:
@bors retry |
| 2025-08-06 04:35:48 |
144979 |
@bors r- retry
yield to the LLVM upgrade, it's in cache |
| 2025-08-06 04:35:24 |
143684 |
@bors retry |
| 2025-08-05 15:24:18 |
144952 |
Looks like "retry r-" is understood as "r-" and got the PR kicked out of the queue. I'll just "retry" it (hope I'm not contradicting something you did on purpose).
@bors retry |
| 2025-08-05 15:18:57 |
144952 |
@bors retry r- |
| 2025-08-05 14:48:32 |
144952 |
@bors retry r- |
| 2025-08-05 01:52:52 |
144887 |
Yielding to enclosing roillup #144934
@bors retry |
| 2025-08-04 19:07:05 |
144898 |
@bors retry |
| 2025-08-04 12:19:22 |
144898 |
@bors retry (yield to stable PR) |
| 2025-08-04 12:19:08 |
144895 |
@bors retry |
| 2025-08-04 09:48:45 |
144891 |
@bors retry (yield to stable release) |
| 2025-08-04 08:22:00 |
144887 |
Yielding to enclosing rollup:
@bors retry |
| 2025-08-04 04:59:51 |
144322 |
@bors retry |
| 2025-08-04 01:26:56 |
144322 |
Yielding to rollup, and also bors is a bit confused:
@bors retry |
| 2025-08-04 01:26:28 |
144042 |
@bors retry |
| 2025-08-03 19:58:43 |
144843 |
Absorbed into #144869
@bors retry |
| 2025-08-03 03:54:02 |
143900 |
Yielding to enclosing rollup (#144845) again:
@bors retry |
| 2025-08-03 03:35:44 |
143900 |
Yielding to enclosing rollup (#144844):
@bors retry |
| 2025-08-02 18:23:42 |
144774 |
@bors retry
apple runner failed: 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.
|
| 2025-08-01 07:49:16 |
144458 |
@bors retry |
| 2025-07-31 22:05:59 |
144446 |
Looks like some kind of network issue.
@bors retry |
| 2025-07-31 05:42:49 |
135975 |
Yielding to enclosing rollup:
@bors retry |