Homu retry log - rust

@bors retry

Looks like some kind of network issue.

@bors retry

Yielding to enclosing rollup:

@bors retry

Failed while uploading artifacts to S3.
@bors retry

I can't find the error.
@bors retry 

Yielding to rollup:

@bors retry

Yielding to enclosing rollup: #144633

@bors retry

Hmm, looks like some spurious GH errors.

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

wtf bors
@bors r- retry

@bors retry r-

looks like ci never started in the past 5 hours? :thinking: 

@bors retry

`arm-android` timeout
@bors retry

@bors retry r- (manual status refresh, maybe github outage yesterday?)

@bors retry r- (this is already merged?)

@bors retry spurious compiletest aux build issue (https://github.com/rust-lang/rust/issues/144237)

> fatal: unable to access 'https://github.com/rust-lang/rust/': Failed to connect to github.com > port 443 after 135716 ms: Couldn't connect to server
> Error: Process completed with exit code 128.

@bors retry

@bors retry spurious network error

The CI runner couldn't find the way back to home 😔 

>  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

Given that this is still quite early, we can yield to to the P-critical. Also I thought the spellcheck was blocking, but it wasn't so...

@bors p=5
@bors retry (yielding to P-critical fix)

@bors retry

@bors retry lost communication with the runner

@bors retry

@bors p=5 retry

@bors retry

@bors p=5 retry

@bors p=5 retry

Still failing, `auto - x86_64-mingw-2` this time but same reason.

@bors p=5 retry

@bors p=5 retry

@bors retry error: could not lock config file C:/msys64/home/runneradmin/.gitconfig: No such file or directory

@bors p=5 retry

@bors retry p=101

In case the spurious CI problem (if it is one) gets (auto-)fixed.

@bors retry

> could not lock config file C:/msys64/home/runneradmin/.gitconfig: No such file or directory

what da heck

@bors retry

@bors retry

Failed because of disk space availability!

https://github.com/rust-lang/rust/actions/runs/16300575917/job/46033948125

@bors retry

@bors retry r-

@bors retry r-

@bors retry

> The hosted runner lost communication with the server.

@bors retry

@bors retry spurious network error

@bors r- retry

@bors retry

@bors retry

@bors retry

@bors retry thread '[ui] tests/ui/rust-2018/removing-extern-crate-malformed-cfg.rs' panicked at src/tools/compiletest/src/runtest.rs:1921:47:

no idea what is up with that test...

spurious?

@bors retry

@bors retry tests\run-make\short-ice spurious failure

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

looks like its stuck
@bors retry r-

![image](https://github.com/user-attachments/assets/1ed2cba0-f394-42af-8ed0-b48106df5eb6)
:thinking: 
@bors retry r-

Yielding to https://github.com/rust-lang/rust/pull/142774
@bors retry

@bors retry

@bors retry

Seems like short-ice might be flaky on Windows?

The Cargo PR merged

@bors retry

I learned on Zulip that you can see this is just a runner fluke https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/molasses.20dist-x86_64-musl.20try-build/near/525099247

@bors retry

Looks like some spurious Windows file path error..

@bors retry