Homu retry log - rust

@bors retry

Spurious, what the-. @bors retry

@bors retry

No idea what this is, npm temporarily unavailable...?

@bors retry

@bors retry (mingw)

@bors retry

@bors retry (msvc take 2)

@bors retry

@bors retry 

@bors retry

@bors retry

@bors retry

Doesn't seem relevant.

@bors retry

@bors retry

@bors retry

@bors retry
 lets see if this is spurious, I don't see any codegen related changes in the prs, cant repro locally

@bors retry (job failed to pick up)

@bors retry

@bors retry

This PR is having an unfortunate go of it.

@bors retry spurious msvc failure

@bors retry

Looks like more Windows flakiness.

@bors retry

:(

@bors retry

@bors retry (msvc)

@bors retry (msvc)

@bors retry r-

another spurious msvc failure

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

spurious

@bors retry

Can't tell if genuine, retrying
@bors retry

@bors retry

@bors retry

@bors retry

spurrious issue i hope? 

@bors retry

oh right p=28 is more than 20 lol...
@bors retry

@bors retry

yielding to a last minute stable release backport as there is only a couple days before release

@bors retry

@bors retry

tests\run-make\avr-rjmp-offset hung on x86_64-mingw

@bors retry msvc moment

@bors retry
Yield priority to the stable release.

@bors retry

@bors retry

Timed out?

@bors retry (failed to pay msvc taxes)

@bors retry (spurious miri failure)

@bors retry

this looks like some spurious miri crash ive seen in the past

Yield to rollup

@bors retry

@bors retry

@bors retry (not even trying)

@bors retry because it smells like a random linker crash

```
Run src/ci/scripts/setup-upstream-remote.sh
Configuring https://github.com/rust-lang/rust remote as upstream.
fatal: unable to access 'https://github.com/rust-lang/rust/': Failed to connect to github.com port 443: Connection timed out
```
@bors retry Failed to connect to github.com port 443: Connection timed out

@bors retry (msvc moment)

@bors retry (msvc)

@bors retry (msvc)

That doesn't look like a failure from this change

@bors retry

@bors retry

@bors retry p=9

@bors retry

msvc debuginfo issue: https://github.com/rust-lang/rust/issues/133107

@bors retry

msvc debuginfo issue

@bors retry

@bors retry

Seriously
@bors retry

debuginfo-cdb failure doesn't seem to be a Cargo issue

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

Pinned `cc` in `library` which seems to fix it. Will follow up and try and figure out the `cc` issue

@bors retry

```
  = note: LINK : fatal error LNK1104: cannot open file 'C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\deps\rustc_main-d22c8966e7ff84ff.exe'␍
```
@bors retry

@bors retry

@bors retry (msvc gaming)

seems spurious?

@bors retry

@bors r=onur-ozkan  retry

@bors r- retry

@bors retry r- (yielding priority to a revert to fix a bootstrap issue)

@bors retry (msvc job couldn’t create temp dir)

@bors retry

@bors retry (unrelated timeout)

lol that definitely has nothing to do with opaques

@bors retry

@bors retry

> ```
> xcode-select: error: invalid developer directory '/Applications/Xcode_14.3.1.app'
> ```

Possibly spurious?

@bors retry

@bors retry

@bors retry

The musl job timed out?

@bors retry

@bors retry

@bors retry

@bors retry r-

@bors retry LLVM rebuild timeout

@bors retry

@bors retry (msvc spurious linker failure)

@bors retry

It looks like some CI jobs are dying, perhaps related to @raoulstrackx's comment above

1000 threads _is_ a lot, are we actually spawning that many for any other tests? I took a quick look and it seemed like the max we had was around 10, that number probably needs to be cut down.

@bors r- retry

@bors retry