| 2025-12-15 03:51:38 |
149999 |
@bors retry |
| 2025-12-13 21:47:27 |
149956 |
@bors retry |
| 2025-12-13 18:49:27 |
149273 |
Guess it was a spurious failure on github's side.
@bors retry |
| 2025-12-12 05:18:43 |
149891 |
@bors retry |
| 2025-12-11 20:31:08 |
149872 |
@bors retry r-
Killing in favour of bigger rollup https://github.com/rust-lang/rust/pull/149890 |
| 2025-12-11 20:27:08 |
149831 |
can you even cancel a bors merge lol
@bors retry
? |
| 2025-12-11 16:32:17 |
149831 |
@bors retry |
| 2025-12-11 10:15:44 |
149831 |
@bors retry (timeout) |
| 2025-12-10 17:27:46 |
149853 |
@bors retry |
| 2025-12-09 21:32:38 |
149818 |
@bors retry |
| 2025-12-09 02:01:51 |
149796 |
@bors retry (network request failed) |
| 2025-12-07 07:22:15 |
149657 |
Seems like some AWS CodeBuild issues?
@bors retry |
| 2025-12-06 21:41:08 |
149657 |
@bors retry |
| 2025-12-05 17:00:44 |
148823 |
@bors retry |
| 2025-12-03 19:25:00 |
149603 |
@bors retry r- |
| 2025-12-03 19:20:05 |
149603 |
@bors retry |
| 2025-12-03 19:18:33 |
149603 |
@bors retry
Cloning into 'rust-toolstate'...
remote: Internal Server Error
fatal: unable to access 'https://github.com/rust-lang-nursery/rust-toolstate/': The requested URL returned error: 500<
|
| 2025-12-03 18:34:01 |
149586 |
> fatal: unable to access 'https://github.com/rust-lang/gcc.git/': The requested URL returned error: 403
@bors retry |
| 2025-12-03 11:40:51 |
149589 |
@bors retry |
| 2025-12-03 07:32:56 |
149581 |
@bors retry |
| 2025-12-03 01:00:31 |
149528 |
Huh. Maybe transient git operation issue?
@bors retry |
| 2025-12-03 00:48:32 |
149528 |
> fatal: unable to access 'https://github.com/rust-lang/cargo.git/': The requested URL returned error: 403
> fatal: clone of 'https://github.com/rust-lang/cargo.git' into submodule path '/home/runner/work/rust/rust/src/tools/cargo' failed
> Failed to clone 'src/tools/cargo' a second time, aborting
The command has failed after 5 attempts.
@bors retry |
| 2025-12-02 17:01:45 |
149456 |
@bors retry |
| 2025-12-01 14:17:58 |
149479 |
@bors retry |
| 2025-12-01 13:20:39 |
149102 |
@bors retry |
| 2025-12-01 07:43:51 |
149481 |
@bors retry |
| 2025-11-30 20:48:20 |
149463 |
@bors retry |
| 2025-11-30 02:17:39 |
149179 |
Bors, this is already merged.
@bors r- retry |
| 2025-11-30 02:17:35 |
149135 |
Bors, this is already merged.
@bors r- retry |
| 2025-11-30 02:17:13 |
149197 |
Bors, this is already merged.
@bors r- retry |
| 2025-11-29 10:12:55 |
149409 |
Yielding to enclosing rollup.
@bors retry |
| 2025-11-29 03:25:02 |
149409 |
@bors retry |
| 2025-11-28 17:24:32 |
149419 |
@bors retry |
| 2025-11-28 09:16:45 |
148020 |
@bors retry yarnpkg returned an internal server error |
| 2025-11-27 16:09:59 |
149382 |
@bors retry r-
|
| 2025-11-27 16:04:10 |
149382 |
@lnicola `@bors retry r-` should stop the ci jobs if you want to do that |
| 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 |