2022-07-02 05:44:05 |
98791 |
Error logs say:
```
2022-07-02T03:26:43.1590283Z Caused by:
2022-07-02T03:26:43.1590916Z [7] Couldn't connect to server (Failed to connect to static.crates.io port 443 after 8192 ms: Network is unreachable)
```
Seems unrelated to whatever error rust-log-analyzer found...?
@bors retry |
2022-07-01 10:16:59 |
98730 |
@bors retry network failure
````
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
39 32.7M 39 13.0M 0 0 154M 0 --:--:-- --:--:-- --:--:-- 156M
curl: (56) OpenSSL SSL_read: Connection was reset, errno 10054
on [auto (dist-i686-msvc, --build=i686-pc-windows-msvc --host=i686-](https://github.com/rust-lang-ci/rust/runs/7146344208?check_suite_focus=true#logs)
```` |
2022-07-01 08:15:49 |
98730 |
@bors retry auto (dist-arm-linux, ubuntu-20.04-xl) hang during artifact upload |
2022-07-01 04:21:08 |
85673 |
@bors retry 0curl: (6) Could not resolve host: ci-mirrors.rust-lang.org |
2022-07-01 04:01:52 |
98730 |
@bors retry artifact upload timeout |
2022-06-30 22:21:20 |
98706 |
@bors retry timeout |
2022-06-30 16:44:20 |
98706 |
let's try this again :upside_down_face: @bors retry |
2022-06-30 16:27:14 |
98706 |
@bors retry yielding to rollup which contains it ^ |
2022-06-29 15:28:33 |
98520 |
@bors retry [dist-apple-various](https://github.com/rust-lang-ci/rust/runs/7111876909?check_suite_focus=true#logs) just stopped? |
2022-06-28 14:30:19 |
98426 |
@bors retry |
2022-06-28 13:31:37 |
98612 |
@bors retry |
2022-06-28 11:35:56 |
98376 |
@bors retry |
2022-06-28 08:48:39 |
98605 |
@bors retry |
2022-06-27 15:00:22 |
98566 |
@bors retry hang while Updating crates.io index on arm-android |
2022-06-27 13:36:30 |
98572 |
@bors retry yield priority to stable release |
2022-06-27 13:36:15 |
98571 |
@bors retry spurious |
2022-06-27 08:46:00 |
98350 |
@bors retry |
2022-06-26 09:21:13 |
98462 |
@bors retry |
2022-06-26 00:51:05 |
98505 |
@bors retry "the runner has received a shutdown signal" hopefully spurious? |
2022-06-25 14:24:41 |
98412 |
@bors retry |
2022-06-25 08:46:21 |
98480 |
@bors retry |
2022-06-24 23:17:41 |
98459 |
@bors retry hang on crates io index checkout? |
2022-06-24 02:08:47 |
98397 |
@bors retry
dist-x86_64-linux-alt is hung at 5 hours
|
2022-06-23 23:36:02 |
98350 |
That failure is the one that caused the tree closure. Should be resolved now.
@bors retry |
2022-06-23 21:39:13 |
98421 |
@bors retry p=10 |
2022-06-23 13:22:16 |
98381 |
a try build has succeeded a short while ago, so let's see if this has been fixed altogether
@bors retry |
2022-06-23 06:51:33 |
98381 |
@bors retry |
2022-06-23 04:53:15 |
98414 |
> curl: (22) The requested URL returned error: 504
@bors retry |
2022-06-23 01:36:46 |
98140 |
@bors retry |
2022-06-23 00:38:42 |
98381 |
@bors retry let's try again? |
2022-06-22 18:30:39 |
98381 |
@bors retry |
2022-06-22 17:07:45 |
93700 |
@bors retry |
2022-06-22 16:32:17 |
98381 |
let's see if it's fixed
@bors retry |
2022-06-22 16:17:16 |
97437 |
@bors retry
GitHub is having issues, returned a 504 |
2022-06-22 15:45:56 |
98381 |
@bors retry |
2022-06-22 15:31:57 |
98386 |
@bors retry |
2022-06-22 15:16:03 |
98381 |
@bors p=1000
@bors retry
tree closed due to [504 issue](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/504.20in.20CI) |
2022-06-22 15:06:30 |
98212 |
GH network issues
@bors retry |
2022-06-22 15:01:53 |
98381 |
@bors retry |
2022-06-22 14:55:01 |
98386 |
@bors retry |
2022-06-22 09:12:24 |
91264 |
@bors retry |
2022-06-22 00:36:21 |
98140 |
@bors retry |
2022-06-21 06:50:41 |
97657 |
@bors retry timeout |
2022-06-20 18:36:57 |
97657 |
@bors retry make[3]: *** No rule to make target `/Users/runner/work/rust/rust/src/llvm�%�x��0��=¤� � _���YJ֗Ξ�� x��R6E�K��!)n�����', needed by `lib/sanitizer_common/CMakeFiles/RTSanitizerCommonSymbolizer.osx.dir/sanitizer_symbolizer.cpp.o'. Stop. |
2022-06-17 05:28:31 |
97892 |
@bors retry |
2022-06-16 02:15:50 |
98144 |
@bors retry r- |
2022-06-15 22:26:33 |
98144 |
@bors retry |
2022-06-15 15:01:24 |
97665 |
yep it's spurious
@bors retry |
2022-06-14 22:52:41 |
98084 |
@bors retry |
2022-06-13 20:15:54 |
95897 |
This smells like it could be unrelated to this PR in any way.
@bors retry |
2022-06-12 06:43:12 |
97993 |
@bors retry spurious failure |
2022-06-11 15:08:37 |
95880 |
@bors retry |
2022-06-11 15:08:17 |
97989 |
@bors retry (spurious) |
2022-06-11 08:58:46 |
95880 |
@bors retry |
2022-06-10 21:51:15 |
97905 |
A double free, huh. But there's no unsafe code in this patch and it doesn't seem related...
@bors retry |
2022-06-08 18:06:57 |
97740 |
```
---- [ui] src/test/ui/abi/anon-extern-mod.rs stdout ----
error: test compilation failed although it shouldn't!
status: signal: 9 (SIGKILL)
```
This cannot really be caused by this PR, right?
@bors retry apple builder failure in src/test/ui/abi/anon-extern-mod.rs |
2022-06-07 23:32:18 |
97701 |
I'm not entirely sure why that test failed 🤔
Just in case it's transient:
@bors retry |
2022-06-07 19:10:59 |
97772 |
Another spurious failure...
@bors retry |
2022-06-07 14:14:05 |
97772 |
Network error.
@bors retry |
2022-06-07 07:15:05 |
97512 |
@bors retry
This doesn't look like something that could have been caused by me:
> I/O error: operation failed to complete synchronously
|
2022-06-06 23:58:16 |
97801 |
Some rustdoc test failure...?
```
---- [rustdoc] src/test\rustdoc\primitive\no_std.rs stdout ----
thread '[rustdoc] src/test\rustdoc\primitive\no_std.rs' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 5, kind: PermissionDenied, message: "Access is denied." }', src\tools\compiletest\src\runtest.rs:2283:34
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
[rustdoc] src/test\rustdoc\primitive\no_std.rs
```
@bors retry |
2022-06-03 23:43:51 |
97717 |
@bors retry ? :upside_down_face: |
2022-06-03 08:10:33 |
89862 |
@bors retry |
2022-06-02 01:54:45 |
97414 |
@bors retry msvc access denied in rustdoc tests
Seems likely to be spurious. |
2022-06-01 16:29:32 |
97612 |
@bors retry |
2022-06-01 10:01:39 |
97612 |
@bors retry |
2022-06-01 01:22:49 |
97435 |
@bors retry rollup=never (perf impact possible though unlikely) |
2022-05-31 12:36:23 |
97419 |
@bors retry spurious network issue |
2022-05-29 23:25:47 |
97493 |
@bors retry yield to rollup |
2022-05-29 23:24:51 |
97419 |
@bors retry (kick it off the queue) |
2022-05-29 23:04:00 |
97419 |
@bors retry yield to rollup |
2022-05-29 19:42:35 |
97493 |
Kicking out of bors queue
@bors retry |
2022-05-29 13:46:44 |
94214 |
@bors retry spurious network error |
2022-05-29 13:38:49 |
97214 |
@bors retry armhf-gnu remote client connection reset |
2022-05-28 08:44:58 |
97137 |
@bors retry |
2022-05-28 07:26:06 |
97383 |
@bors retry |
2022-05-28 02:36:22 |
97284 |
@bors retry spurious network error |
2022-05-27 18:33:11 |
97214 |
@bors retry
`The operation was canceled.` for dist-aarch64-linux near the beginning of the build, but it was never marked as failed.
|
2022-05-27 15:16:49 |
97284 |
@bors retry maybe spurious?
|
2022-05-27 09:14:34 |
97327 |
This seems pretty spurious.
@bors retry |
2022-05-26 21:33:45 |
97386 |
@bors retry |
2022-05-26 19:00:23 |
97383 |
@bors retry |
2022-05-26 15:13:52 |
97427 |
@bors retry |
2022-05-26 03:00:15 |
97410 |
@bors retry |
2022-05-25 21:43:25 |
97369 |
@bors retry |
2022-05-25 05:29:59 |
94954 |
@bors retry |
2022-05-24 10:25:07 |
95953 |
Failed in rollup: https://github.com/rust-lang/rust/pull/97347#issuecomment-1135718551
Needs to ignore some targets on the tests
@bors retry r- |
2022-05-24 01:12:06 |
97272 |
@bors retry seems unrelated |
2022-05-22 16:47:12 |
97254 |
@bors retry aarch64-gnu seems stuck
It's been running for over 2.5 hours when normally it takes <50 mins. |
2022-05-21 17:12:08 |
97248 |
@bors retry |