Homu retry log - rust

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))

@bors retry

@bors retry

@bors retry mysql error

@bors retry (after #137041)

@bors retry (after #137041)

@bors retry
(after #137041)

@bors retry (remote-test-client spurious)

@bors retry

(Trying to poke bors into being less confused without a full resync.)

yielding once to retry the rollup of this, to see if its failure was spurious
@bors retry

@bors retry

@bors r- retry

https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/bors.20stuck.3F.20.282025-02-09.29

Timeout at:

> test [debuginfo-lldb] tests/debuginfo/destructured-for-loop-variable.rs has been running for a long time

does not seems to be related to any PRs here. Maybe also spurious. Let's try again.

@bors retry

praying for spurious?

@bors retry

@bors retry

@bors retry

> A job failed! Check out the build log: [(web)](https://github.com/rust-lang-ci/rust/actions/runs/13207740122/job/36874797119) [(plain)](https://github.com/rust-lang-ci/rust/commit/433a03d4c162ec33256a31ffd91f9506348a3454/checks/36874797119/logs)
> 
> Click to see the possible cause of the failure (guessed by this bot)
> ```
> 
> ```

What the hack?

@bors retry

@bors retry

@bors retry npm segv

```
Warning: Failed to download action 'https://api.github.com/repos/msys2/setup-msys2/tarball/cc11e9188b693c2b100158c3322424c4cc1dadea'. Error: Response status code does not indicate success: 502 (Bad Gateway). 2000:2149E5:1A91644:3570737:67A48FEC
```

@bors retry

spurious @bors retry

spurious @bors retry 

```
2025-02-05T15:05:39.4205610Z /home/runner/work/_temp/b5a68acc-aeff-4e08-87aa-c411406e4756.sh: line 2: 559548 Segmentation fault      (core dumped) npm ci
```

Can I help you?

@bors retry

Likely spurious

@bors retry llvm-tblgen crashed while building LLVM

@bors retry (maybe network failure?)

```
   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 96 5495k   96 5285k    0     0  35.5M      0 --:--:-- --:--:-- --:--:-- 36.0M
curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
Error: Process completed with exit code 56.
```

@bors retry (network failure?)

@bors retry

yeah looks like CI is toast... :bread: 
@bors retry

@bors retry various systemd timeouts on aarch64-gnu-debug?

@bors retry  yield rollup

@bors retry

i686-msvc-1 tests\codegen\asm\sparc-clobbers.rs#sparc failed to create temp dir, access denied.

> tests/ui/threads-sendsync/tcp-stress.rs

@bors retry rollup=iffy

I'm going to hope that's a spurious test failure.

@bors retry

> `` error: failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\rustc-main.exe` ``

I can't believe it!!

@bors retry

Jeeeeez!! @bors retry

[auto - dist-loongarch64-linux](https://github.com/rust-lang-ci/rust/actions/runs/13095618139/job/36537583414#logs) :frowning_face: 

@bors retry

@bors retry

```
thread 'main' has overflowed its stack
```

That seems weird. It might just be a spurious error but I'm not sure. Let's see if it fails twice:

@bors retry

@bors retry

@bors retry

I don't think windows-2025 is going to make a difference here. I'm seeing max-rss of ~2G on that TableGen invocation locally, so it does seem plausible that this could go OOM on i686, especially if parallelism is involved.

Testing a patch to cut memory usage down a bit, though it's only by about 100MB...

@bors retry

Let's see if we can get past the OOM...

@bors retry

@bors retry

@bors r- retry

Job looks stuck

@bors retry

@bors retry runner crash

@bors retry

probably spurious?
```
     Compiling rustc-std-workspace-core v1.99.0 (D:\a\rust\rust\library\rustc-std-workspace-core)
  
  thread 'main' has overflowed its stack
```

@bors retry

https://github.com/rust-lang/rust/pull/136023 was merged.

@bors retry

bors why

@bors r- retry

@bors retry

@bors retry

@bors retry spurious failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-rustc\x86_64-pc-windows-msvc\release\rustc-main.exe`