Homu retry log - rust

@bors retry The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is cancelled.

```
2025-04-23T11:21:31.7487080Z error: couldn't create a temp dir: Access is denied. (os error 5) at path "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustcvYNGC6"
2025-04-23T11:21:31.7487640Z 
2025-04-23T11:21:31.7487822Z error: aborting due to 1 previous error
```

@bors retry

@bors retry couldn't create a temp dir: Access is denied

@bors retry

@bors retry

@bors retry spurious linking with `rust-lld` failed: exit code: 0xc0000374

@bors r- retry (#140091 might mask real issues)

@bors retry

@bors retry spurious Windows error

@bors retry

```
failed to remove and recreate output directory `/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/mir-opt/strip_debuginfo`: Directory not empty (os error 66)
```
Seems spurious, and no bumped deps seem relevant
@bors retry

I could be wrong but that looks spurious to me. None of the PRs should cause librustc_driver not to be found when documenting stage 2. Let's try again

@bors retry Library not loaded: @rpath/librustc_driver-083a5cd6fc07d78e.dylib

spurious

@bors retry

@bors retry failed to remove and recreate output directory 

@bors retry network error

seems spurious

@bors retry couldn't create a temp dir: Access is denied

@bors retry
` failed to remove and recreate output directory `C:\a\rust\rust\build\x86_64-pc-windows-msvc\test\mir-opt\strip_debuginfo`: Access is denied. (os error 5)

@bors retry

@bors retry

@bors retry
```
2025-04-18T19:12:34.8633667Z    Compiling foo v0.1.0 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\tmp\cit\t245\foo)
2025-04-18T19:12:34.8634860Z    Compiling bar v0.1.0 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\tmp\cit\t245\foo\bar)
2025-04-18T19:12:34.8636135Z error: couldn't create a temp dir: Access is denied. (os error 5) at path "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustccfrkMc"
2025-04-18T19:12:34.8636837Z
2025-04-18T19:12:34.8637137Z error: could not compile `foo` (bin "foo") due to 1 previous error

``

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

Yet another flaky temp dir failure.

@bors retry

```
2025-04-13T03:57:03.7507822Z thread 'main' panicked at src/tools/remote-test-client/src/main.rs:309:9:
2025-04-13T03:57:03.7509260Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
2025-04-13T03:57:03.7510193Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

@bors retry

couldn't create a temp dir

@bors retry

> error: couldn't create a temp dir: Access is denied.

@bors retry

@bors retry

@bors retry

@bors retry mingw failed as usual 

@bors retry

@bors retry

added to the rollup

Spurious perm error.
@bors retry

@bors retry

Thank you bors, I noticed.
@bors retry

@bors retry  

closed the overlapping rollup 

@bors retry

@bors retry
https://github.com/rust-lang/rust/issues/137938 rust-lld fails with 0xc0000374

> (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

Given this, and the fact that this failed relatively early, I'm going to retry and cross my fingers:

@bors retry

I suspect this is not spurious, but giving it a retry
@bors retry

That failure seems bogus.

@bors retry

@bors retry

@bors retry

@bors retry 

netwotk problems @bors retry

ugh race condition @bors r- retry

@bors retry

@bors retry

@bors retry

This is the same failure as the previous time (maybe due to OOM?), but let's try again.
@bors retry

Seems unrelated to this PR.

@bors retry

looks spurious

@bors retry

Job not picked up
@bors retry

@bors retry

The error seems not related to the pull requests. @bors retry

@bors retry GHA internal error

@bors r- retry

@bors retry r-

>>> warning: spurious network error (3 tries remaining): [28] Timeout was reached (download of `object v0.36.7` failed to transfer more than 10 bytes in 30s)
  warning: spurious network error (3 tries remaining): [28] Timeout was reached (failed to download any data for `adler2 v2.0.0` within 30s)
  warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of `object v0.36.7` failed to transfer more than 10 bytes in 30s)
  warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for `adler2 v2.0.0` within 30s)
    Downloaded adler2 v2.0.0
  warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for `object v0.36.7` within 30s)
  error: failed to download from `[https://static.crates.io/crates/object/0.36.7/download`](https://static.crates.io/crates/object/0.36.7/download%60)

Spurious
@bors retry

Sorry, bootstrap CI LLVM is broken atm re. perf.
@bors retry r-
@bors treeclosed=100

Sorry, perf and CI LLVM is a bit broken atm. Please re-approve once bootstrap & perf is fixed.
@bors retry r-

@bors r- retry

yield to larger rollup

@bors retry

@bors retry

@bors retry network error crates io

@bors retry

@bors retry

@bors retry

@bors retry

@rustbot ping fuchsia
This is the second fuchsia error in a row. In a PR that's juts a revert, so this kind of has to be spurious, right? No PR landed since ~6h ago so seems like CI might just be broken by the fuchsia job right now?

@bors retry odd fuchsia error

@bors retry

@bors retry Fuchsia networking issue 

@bors retry

@bors retry

@bors retry

@bors retry

That failure seems spurious...
@bors retry

dead runner?

@bors retry

Ok, looks good.

@bors retry

@bors retry

More Windows segfaults..

```
2025-03-14T00:40:22.1512202Z --- stderr -------------------------------
2025-03-14T00:40:22.1580734Z error: couldn't create a temp dir: Access is denied. (os error 5) at path "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustcfzdxGW"
2025-03-14T00:40:22.1581195Z 
2025-03-14T00:40:22.1581369Z error: aborting due to 1 previous error
2025-03-14T00:40:22.1581672Z ------------------------------------------
```
@bors retry (x86_64-pc-windows-gnu transient Windows filesystem access issue)

That looked like a spurious network error.

@bors retry

This is a classic MSVC spurious failure.
@bors retry

The failure doesn't seem relevant to this PR.

@bors retry

@bors retry