Homu retry log - rust

@bors retry spurious

GitHub Actions had an incident last night (a different one), https://www.githubstatus.com/incidents/c7kq3ctclddp

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

This has merge conflicts.
@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

Bors hasn't noticed that this was merged.

@bors r- retry

GitHub is once again refusing to show useful logs, so I'm going to assume that the GHA runners exploded again.

@bors retry

@bors retry

Given that this succeeded in the past, and that GitHub won't even let me see the failure logs, I think it's reasonable to assume yet more CI flakiness.

@bors retry

Even if this job spontaneously becomes unstuck, it's still not going to finish in under 6 hours. Better to reroll the CI dice now.

@bors retry

@bors retry

https://github.com/rust-lang/rust/runs/48262739268

didn't finish the job without any obvious errors

@bors retry (msvc timeout)

https://github.com/rust-lang/cargo/pull/15851 should unblock loongarch64.

@bors retry

@bors r- retry

@bors retry

Yield to rollup=never; I'll make a rollup including this PR soon enough.

@bors retry

Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))

@bors retry

Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))

@bors retry

Network failure ([#t-infra > Non-stop network timeouts across auto-builds](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/Non-stop.20network.20timeouts.20across.20auto-builds))

@bors retry

Network o.O ... again! At least 3 PRs have failed due to network issues in the last <24 hours, might need to bring this to T-infra...

@bors retry

@bors retry (flaky)

spurious? submodule checkouts never terminated or had some other failure, can't see the full logs

@bors retry

@bors retry (flaky download failure?)

unrelated

@bors retry

@bors retry (flaky)

presumably that is spurious

@bors retry

@bors retry Same reserved_windows_name failure also happened on https://github.com/rust-lang/rust/pull/145161 recently.

@bors retry Not super clear what actually failed there, but it looks spurious.

@bors retry (flaky?)

Looks mega spurious.

@bors retry

I think #144544 is failing?
@bors r- retry

@bors retry

> `client.read_exact(&mut header) failed with Connection reset by peer (os error 104)`

https://triage.rust-lang.org/gha-logs/rust-lang/rust/47726534304#2025-08-09T07:27:09.9986295Z

seems spurious?

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry float precision failure 

Yield to never PRs while we figure out why the rollup failed.

@bors retry

Yielding to enclosing rollup:

@bors retry

@bors r- retry

yield to the LLVM upgrade, it's in cache

@bors retry

Looks like "retry r-" is understood as "r-" and got the PR kicked out of the queue. I'll just "retry" it (hope I'm not contradicting something you did on purpose).

@bors retry

@bors retry r-

@bors retry r-

Yielding to enclosing roillup #144934
@bors retry

@bors retry

@bors retry (yield to stable PR)

@bors retry

@bors retry (yield to stable release)

Yielding to enclosing rollup:

@bors retry

@bors retry

Yielding to rollup, and also bors is a bit confused:

@bors retry

@bors retry

Absorbed into #144869
@bors retry

Yielding to enclosing rollup (#144845) again:

@bors retry

Yielding to enclosing rollup (#144844):

@bors retry

@bors retry

apple runner failed: 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

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