| 2025-11-27 04:34:32 |
148987 |
> The hosted runner lost communication with the server.
Tragic. @bors retry |
| 2025-11-26 06:35:12 |
148358 |
Let's try again!
@bors retry |
| 2025-11-26 04:17:13 |
147799 |
I can't see raw logs, which means a runner probably flaked out.
@bors retry |
| 2025-11-26 02:11:28 |
149140 |
The `aarch64-apple` job has stalled (5h and counting); better to get the queue moving now than to wait another hour for it to formally time out.
😿
@bors retry |
| 2025-11-25 18:40:35 |
149140 |
@bors retry yarn install did not exit successfully |
| 2025-11-23 10:44:23 |
148925 |
@bors retry |
| 2025-11-23 00:49:38 |
149096 |
not sure whether it is related to the change,
try again:
@bors retry jobs=x86_64-mingw-1 |
| 2025-11-22 15:45:17 |
147536 |
@bors retry yield rollup |
| 2025-11-21 20:40:04 |
149127 |
@bors r- retry |
| 2025-11-21 20:39:55 |
149134 |
@bors r- retry |
| 2025-11-21 20:39:43 |
148990 |
@bors r- retry |
| 2025-11-21 03:45:19 |
148990 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-20 09:37:50 |
149118 |
Github won't show me the actual cause, but I think this is just a spurious failure in `dist-x86_64-msvc`
@bors retry |
| 2025-11-20 01:09:58 |
149118 |
Bors, please start running jobs.
@bors retry |
| 2025-11-19 21:01:30 |
149073 |
@bors retry
Apparently a runner hasn't yet picked up the job, 5 hours in https://github.com/rust-lang/rust/actions/runs/19506679894/job/55834821771 |
| 2025-11-19 13:31:33 |
149073 |
@bors retry
Could not resolve host: github.com |
| 2025-11-18 20:42:25 |
149063 |
@bors retry |
| 2025-11-18 09:54:30 |
149037 |
Hm, maybe networking?
@bors rollup=never
@bors retry |
| 2025-11-18 06:58:14 |
148803 |
Yeah, probably runner went down.
@bors retry |
| 2025-11-16 06:57:36 |
148886 |
Bors no, this is already merged.
@bors r- retry |
| 2025-11-16 06:57:28 |
148735 |
Bors no, this is already merged.
@bors r- retry |
| 2025-11-16 03:41:15 |
148832 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-15 12:32:50 |
148957 |
@bors retry |
| 2025-11-15 08:52:58 |
148954 |
> The self-hosted runner lost communication with the server.
@bors retry |
| 2025-11-14 08:57:49 |
148638 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-14 02:11:10 |
146978 |
@bors retry |
| 2025-11-14 01:56:21 |
147462 |
```
denied: permission_denied: write_package
##[error]Process completed with exit code 1.
```
@bors retry |
| 2025-11-13 15:16:01 |
146978 |
@bors retry |
| 2025-11-12 19:47:48 |
148808 |
@bors r- retry |
| 2025-11-12 05:21:13 |
147804 |
Bors, this PR has merge conflicts.
@bors r- retry |
| 2025-11-12 05:21:03 |
144465 |
Bors, this PR has merge conflicts.
@bors r- retry |
| 2025-11-12 05:19:25 |
146627 |
Bors, this has already been merged.
@bors r- retry |
| 2025-11-12 05:19:06 |
148531 |
Bors, this has already been merged.
@bors r- retry |
| 2025-11-12 01:27:22 |
147974 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-11 10:10:41 |
143619 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-11 09:50:52 |
148813 |
Sorry, https://github.com/rust-lang/rust/pull/147952#issuecomment-3515565316 was r-'d.
@bors retry r- |
| 2025-11-11 06:58:53 |
148813 |
A network request flaked out.
@bors retry |
| 2025-11-11 02:37:04 |
148802 |
Seems like this got stuck. It's be almost 4.5 hours and hasn't made progress in a long while.
@bors r- retry |
| 2025-11-10 13:08:32 |
135634 |
@bors retry |
| 2025-11-10 00:54:56 |
147115 |
@bors retry |
| 2025-11-08 22:38:24 |
148692 |
@bors retry |
| 2025-11-08 16:43:41 |
148692 |
@bors retry network error |
| 2025-11-07 23:36:38 |
148591 |
@bors retry |
| 2025-11-07 23:13:51 |
147803 |
I guess? Somehow? The current PR being tested is definitely seeing the fix so let's try again.
@bors retry |
| 2025-11-07 23:13:01 |
147935 |
@bors retry |
| 2025-11-07 22:18:55 |
148650 |
@bors retry |
| 2025-11-07 22:04:00 |
145656 |
@bors retry
bot opened the tree unexpectedly |
| 2025-11-07 18:55:38 |
145656 |
@bors retry
npm issue: https://github.com/rust-lang/rust/pull/148665 |
| 2025-11-07 18:29:45 |
147029 |
@bors retry |
| 2025-11-07 18:29:14 |
147803 |
@bors retry yield to the close |
| 2025-11-07 18:18:36 |
147803 |
@bors retry |
| 2025-11-07 17:16:29 |
148650 |
@bors retry |
| 2025-11-07 03:35:06 |
148593 |
This time a different runner flaked out.
@bors retry |
| 2025-11-07 02:14:17 |
148593 |
One of the runners (`aarch64-apple`) stalled and is very unlikely to finish before the timeout. 😿
It'll be faster to retry this PR now, before it hits the 6 hour mark.
@bors retry |
| 2025-11-06 08:43:13 |
148188 |
Runner flaked out.
@bors retry |
| 2025-11-06 01:53:36 |
147935 |
Failure in `rustdoc-gui` looks bogus.
@bors retry |
| 2025-11-05 04:21:23 |
148507 |
GitHub Actions isn't showing full logs for the failed job, so treating it as runner flakiness. 😿
@bors retry |
| 2025-11-04 16:37:46 |
148471 |
@bors retry |
| 2025-11-04 12:08:02 |
144529 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-04 12:00:39 |
145915 |
@bors r- retry |
| 2025-11-04 02:45:36 |
133149 |
Yielding to enclosing rollup (again).
@bors retry |
| 2025-11-04 02:22:47 |
133149 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-03 06:48:45 |
147728 |
Previous failure seems like flakiness.
@bors retry |
| 2025-11-02 18:00:11 |
148305 |
I... didn't change that code?
@bors retry |
| 2025-11-02 15:27:58 |
148290 |
@bors r- retry |
| 2025-11-02 06:59:07 |
148170 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-02 03:44:04 |
148170 |
Looks like a CI runner flaked out.
@bors retry |
| 2025-11-01 16:43:36 |
148356 |
@bors retry musl timeout |
| 2025-11-01 07:15:35 |
148340 |
@bors retry rollup=iffy |
| 2025-11-01 06:52:30 |
148337 |
@bors retry |
| 2025-11-01 03:53:19 |
148336 |
@bors retry
dist-x86_64-msvc — The self-hosted runner lost communication with the server. |
| 2025-10-31 11:42:15 |
148165 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-30 06:54:22 |
147935 |
@bors r- retry |
| 2025-10-30 02:05:47 |
147935 |
@bors retry |
| 2025-10-28 16:33:09 |
148177 |
@bors retry (yielding to a stable PR) |
| 2025-10-28 13:24:37 |
148178 |
Bors, these PRs have already been merged.
@bors r- retry |
| 2025-10-28 05:07:53 |
148181 |
@bors retry |
| 2025-10-28 03:15:41 |
148178 |
@bors retry
yeh looks spurious, no rustdoc chanpes in here |
| 2025-10-27 11:48:02 |
148154 |
@bors retry
Spurious CI failure, this PR did not touch rustc or mir tests in any way |
| 2025-10-26 11:16:01 |
148097 |
Failed in rollup in `aarch64-msvc-1`: https://github.com/rust-lang/rust/pull/148127#issuecomment-3448429957
@bors r- retry |
| 2025-10-25 16:29:09 |
148100 |
@bors retry |
| 2025-10-25 06:40:44 |
148075 |
No apparent error, just stopped while scraping licenses...
@bors retry |
| 2025-10-24 17:39:30 |
148073 |
Yielding to #148018 as it's release-relevant...
@bors retry |
| 2025-10-24 16:48:17 |
148065 |
Network.
> received unexpected HTTP status: 504 Gateway Timeout
@bors retry |
| 2025-10-24 09:45:17 |
147775 |
Bors why are you showing this as the current test
@bors r- retry |
| 2025-10-23 21:31:08 |
148018 |
@bors r- retry
Failed https://github.com/rust-lang/rust/pull/148041
|
| 2025-10-20 10:17:41 |
147734 |
Docker appears to be working again.
@bors retry |
| 2025-10-20 10:16:21 |
142696 |
Docker appears to be working again.
@bors retry |
| 2025-10-20 09:08:16 |
142696 |
@bors retry |
| 2025-10-20 05:15:40 |
146167 |
Yielding to enclosing rollup.
@bors retry |
| 2025-10-19 17:17:22 |
147575 |
@bors retry yield https://github.com/rust-lang/rust/pull/147884 |
| 2025-10-19 17:16:51 |
147884 |
@bors retry
https://github.com/rust-lang/rust/issues/147885 |
| 2025-10-19 09:45:08 |
147698 |
@bors retry Spurious. |
| 2025-10-17 16:35:41 |
147654 |
@bors retry |
| 2025-10-17 13:11:20 |
147654 |
Probably a spurious failure. See <https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Repeated.20spurious.20failure.20of.20.60x86_64-mingw-1.60/with/545487472>.
@bors retry |
| 2025-10-17 05:34:41 |
147779 |
It looks like the test that made it fail is spuriously failing a lot.
@bors retry |
| 2025-10-17 01:55:48 |
147508 |
@bors retry |
| 2025-10-16 11:44:34 |
147775 |
@bors retry looks spurious
https://github.com/rust-lang/rust/pulls?q=is%3Apr+%22stress_recv_timeout_two_threads%22+is%3Aclosed |