Homu retry log - rust

@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

@bors retry (access denied spurious)

@bors retry
``
2025-03-10T18:36:02.0742736Z thread 'main' panicked at src/tools/remote-test-client/src/main.rs:309:9:
2025-03-10T18:36:02.0743637Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
2025-03-10T18:36:02.0744533Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
``

@bors retry

Seems unrelated 

@bors retry

@bors retry

I can't seem to repro this locally on mingw. Let's see if it's spurious; I'll open an issue to track this.

@bors retry

Looks like no luck yet

@bors r- retry

@bors retry

GitHub credits issue.

> The hosted runner encountered an error while running your job. (Error Type: Disconnect).

@bors retry

@bors retry

@bors retry (spurious mingw)

@bors retry

@bors retry

The rfl job is a rustup error and is getting disabled.

@bors retry

@bors retry

@bors retry

Oh... I think that might be a `rust-lld` issue where sometimes it just *dies*.

Let's see on a retry.

@bors retry

@bors retry

@bors retry

Trying again after ~30 minutes.

@bors retry

@bors p=101
@bors retry

@bors retry

@bors retry
@bors treeclosed ghcr network errors

@bors retry

@bors retry network error

sigh..

@bors retry Get "https://ghcr.io/v2/": context deadline exceeded

@bors retry network error

@bors retry spurious network error

@bors retry

 @bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry for the time being 

what the fuck?????
@bors retry 

@bors retry

@bors retry

Yeah sorry meant to do that but got distracted.

@bors r- retry

Unfortunately it looks like dist-powerpc64le-linux is stuck, last log update was two hours ago and all other jobs are complete. I don't think this would be a side effect of the changes here.

@bors r- retry

With the switch to smaller builders, updating CI config now more often ends in timeouts :disappointed: Let's try again.

@bors retry

@bors retry

Sounds spurious.

@bors retry

@bors retry temp for failure on windows

This essentially wiped the sccache cache, and this builder didn't like it, lol. Let's try again with the cache (hopefully) primed.

@bors retry

@bors r- retry

@bors r- retry
There's still something wrong with `tests/codegen/abi-x86-sse.rs`.

@bors retry r- (still in the queue (unapproved ofc))