Homu retry log - rust

Looks like some spurious Windows file path error..

@bors retry

@bors retry

@bors retry

 @bors retry

@bors retry

@bors retry
added to #142421 

@bors r- retry
I'll ge-do the sync to include some more changes.

@bors retry

Cargo change should not affect this part of code 

https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/test-various.20failures

@bors retry

I do not know what those sanitizer errors are about. Cargo should have no effect on those tests (it isn't used), and the job doesn't set download-rustc. The image hasn't changed since the last successful build. 🤷 

@bors retry

Wut?
@bors retry

@bors retry "can't find crate for `std`" `download-ci-rustc` issue

@bors retry run-make/export/compile-interface-error: can't find crate for `std`

This failed the run-make tests?!?  That's weird...

@bors retry 

@bors retry r-

@bors retry

@bors retry

@bors retry dunno, "can't find crate for `std`"

@bors retry
yield to fixing PR CI: https://github.com/rust-lang/rust/pull/141860#issuecomment-2927367549

@bors r- retry
Needs another patch

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-