Homu retry log - rust

@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

@bors r- retry

@bors r- retry

@bors r- retry

That looks.. spurious, but also concerning (heap corruption error?). Let's retry.

@bors retry

@bors retry error: linking with `link.exe` failed: exit code: 1104 on dist-x86_64-msvc

It's as if this PR is *still* being tested, so to be safe:
@bors r- retry

@bors r- retry (nonono this is a try job, do not merge)

@bors r- retry

@bors r- retry (stop this already merged)

@bors r- retry (stop, really)

@bors retry

please stop dying
@bors retry

no @bors retry

I didn't change anything outside of rustdoc.

@bors retry

@bors retry

@bors retry npm error network Invalid response body while trying to fetch

I guess CI couldn't find anything this time so it just made up a failure

@bors retry

seems spurious. @bors retry

don't terminate my batch job D:
@bors retry

@bors retry

This time I actually pushed the change
@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry 

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry (Windows runner was weirdly slow and timed out; probably unrelated to this PR)

@bors retry

(hoping that #131448 lands with its fix)

MSVC failure

@bors retry

Oh - do we not have the mitigations for the MSVC failure on the beta branch?

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry

@bors retry r-

@bors r- retry

@bors r- retry (bors problem)

@bors retry

@bors retry

Build error doesn't look related? @bors retry

@bors retry timeout

@bors retry timeout