Homu retry log - rust

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

@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)
````

@bors retry   auto (dist-arm-linux, ubuntu-20.04-xl)  hang during artifact upload

@bors retry  0curl: (6) Could not resolve host: ci-mirrors.rust-lang.org 

@bors retry artifact upload timeout

@bors retry timeout

let's try this again :upside_down_face:  @bors retry

@bors retry  yielding to rollup which contains it ^

@bors retry [dist-apple-various](https://github.com/rust-lang-ci/rust/runs/7111876909?check_suite_focus=true#logs) just stopped?

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry hang while Updating crates.io index on arm-android

@bors retry yield priority to stable release

@bors retry spurious

@bors retry

@bors retry

@bors retry "the runner has received a shutdown signal" hopefully spurious?

@bors retry

@bors retry

@bors retry hang on crates io index checkout?

@bors retry

dist-x86_64-linux-alt is hung at 5 hours

That failure is the one that caused the tree closure. Should be resolved now.

@bors retry

@bors retry p=10

a try build has succeeded a short while ago, so let's see if this has been fixed altogether

@bors retry

@bors retry

> curl: (22) The requested URL returned error: 504 

@bors retry

@bors retry

@bors retry let's try again?

@bors retry

@bors retry

let's see if it's fixed

@bors retry

@bors retry

GitHub is having issues, returned a 504

@bors retry

@bors retry

@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)

GH network issues
@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry timeout

@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.

@bors retry

@bors retry r-

@bors retry

yep it's spurious 

@bors retry

@bors retry

This smells like it could be unrelated to this PR in any way.

@bors retry

@bors retry spurious failure

@bors retry

@bors retry (spurious)

@bors retry

A double free, huh. But there's no unsafe code in this patch and it doesn't seem related...

@bors retry

```
---- [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

I'm not entirely sure why that test failed 🤔 

Just in case it's transient:

@bors retry

Another spurious failure...

@bors retry

Network error.

@bors retry

@bors retry

This doesn't look like something that could have been caused by me:

> I/O error: operation failed to complete synchronously

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

@bors retry ? :upside_down_face: 

@bors retry

@bors retry msvc access denied in rustdoc tests

Seems likely to be spurious.

@bors retry

@bors retry

@bors retry rollup=never (perf impact possible though unlikely)

@bors retry spurious network issue

@bors retry yield to rollup

@bors retry (kick it off the queue)

@bors retry yield to rollup

Kicking out of bors queue

@bors retry

@bors retry spurious network error

@bors retry armhf-gnu remote client connection reset

@bors retry

@bors retry

@bors retry spurious network error

@bors retry

`The operation was canceled.` for dist-aarch64-linux near the beginning of the build, but it was never marked as failed.

@bors retry maybe spurious?

This seems pretty spurious.

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

Failed in rollup: https://github.com/rust-lang/rust/pull/97347#issuecomment-1135718551
Needs to ignore some targets on the tests

@bors retry r-

@bors retry seems unrelated 

@bors retry aarch64-gnu seems stuck

It's been running for over 2.5 hours when normally it takes <50 mins.

@bors retry