Homu retry log - rust

Same thing,
@bors retry

@bors retry

This is still rollup=maybe so I put it into a rollup https://github.com/rust-lang/rust/pull/141707 (the queue is pretty full)

@bors retry

No reason for this to time out.

@bors retry

@jplatte these could use example doctests at some point, feel free to either add them here or in a follow up.

> I merged the latest changed, squashed and force-push, I don't know why the auto build of this job didn't start. Can we give it another try in the auto build if the try job works?

When the build fails, bors will remove the previous approval, you have to reapprove it or do `retry`.

@bors retry

@bors retry

@bors p=9 retry

@bors retry

@bors retry

@bors retry

Just in case it's somehow spurious.

@bors retry

The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

@bors retry r-

@bors retry powerpc64-unknown-linux-gnu-gcc linker error 

@bors retry (bumping in favour of rollup that includes this PR)

@bors retry (mingw)

@bors retry (yield to rollup, sry)

@bors r- retry https://github.com/rust-lang/rust/pull/141228#issuecomment-2889089079

@bors retry

@bors retry

@bors retry (x86_64-apple `rustc exited with signal: 11 (SIGSEGV)`)

That was fast, let's try again. =D

@bors retry

@bors retry (where d drive problem is known and being worked around)

@bors retry

@bors retry

Spurious, so @bors retry
Hopefully https://github.com/actions/runner-images/issues/12199#issuecomment-2880239709 gets fixed before this is hit again 😅 

`System.IO.IOException: There is not enough space on the disk` - @bors retry

@bors retry (mysterious failures)

@bors retry System.IO.IOException: There is not enough space on the disk. msvc-1

@bors retry

@bors retry (no idea)

@bors retry (no disk space)

@bors retry (not enough space)

@bors r- retry

@bors retry (bors thinks this is still in the queue)

I don't see any failure in the logs, weird. Let's retry...

@bors retry

What? And I can inspect the raw logs. GH why. This has to be spurious
@bors retry

That is

> llvm-tblgen Segmentation fault in CI on dist-aarch64-apple #10962

@bors retry

Bors, are you awake?

@bors retry

Also included https://github.com/rust-lang/rust/pull/140864

@bors retry r+ p=1000 rollup=never

@bors retry
Yield priority to the stable release.

Unfortunately this has merge conflicts.
@bors retry r-

Seems flaky, let's retry.

@bors retry x86_64-mingw-2

@bors retry 

(msvc job couldn’t create temp dir)

https://github.com/rust-lang/rust/pull/132675#issuecomment-2466664810

@bors rollup retry

[The CI job “succeeded” hours ago](https://github.com/rust-lang-ci/rust/actions/runs/14782882110/job/41512999598), but bors seems to be stuck thinking it's still running.

@bors retry

@bors retry r-

@bors retry #97669

@bors retry r-

spurious 

@bors retry x86_64-mingw-1 0xc0000374

@bors retry

@bors r-
@bors retry

@bors retry

CI error is unrelated to this PR. Seems spurious.

@bors retry 

@bors retry

put this in a rollup five minutes too late

*sigh* that's a completely unrelated failure

@bors retry (mingw) error: linking with `rust-lld` failed: exit code: 0xc0000374

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

If this continues to be a pain then you could try to see about backporting c07054bdd1f8927fef5b1665debff9cb27452cc0. Though hopefully that won't be necessary...

@bors retry

@bors retry

@bors retry (msvc; couldn't create a temp dir)

@bors retry rust-lld heap corruption

@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