Homu retry log - rust

Time (UTC) PR Message
2025-03-22 09:07:56 136974
@bors retry
2025-03-21 18:49:50 138580
@bors retry
2025-03-20 20:09:47 138747
@bors retry
2025-03-19 20:59:19 138714
@bors retry
2025-03-18 17:58:19 138661
@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
2025-03-18 16:44:17 138653
@bors retry
2025-03-18 14:46:06 138661
@bors retry Fuchsia networking issue 
2025-03-18 13:30:03 138653
@bors retry
2025-03-18 12:06:06 138515
@bors retry
2025-03-18 05:24:40 138630
@bors retry
2025-03-17 15:56:53 138515
@bors retry
2025-03-17 10:20:47 136929
That failure seems spurious...
@bors retry
2025-03-16 05:07:22 138525
dead runner?

@bors retry
2025-03-15 12:27:12 137665
Ok, looks good.

@bors retry
2025-03-14 13:55:27 138452
@bors retry

More Windows segfaults..
2025-03-14 01:00:29 138157
```
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)
2025-03-13 10:22:19 137665
That looked like a spurious network error.

@bors retry
2025-03-12 23:12:36 138416
This is a classic MSVC spurious failure.
@bors retry
2025-03-12 08:17:07 137612
The failure doesn't seem relevant to this PR.

@bors retry
2025-03-12 07:59:47 138388
@bors retry
2025-03-10 23:48:40 138302
@bors retry (access denied spurious)
2025-03-10 18:40:38 138302
@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
``
2025-03-10 17:37:33 138302
@bors retry
2025-03-08 19:25:01 138200
Seems unrelated 

@bors retry
2025-03-06 20:36:20 138114
@bors retry
2025-03-06 16:50:44 138039
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
2025-03-06 07:36:21 138079
Looks like no luck yet

@bors r- retry
2025-03-06 04:34:30 136780
@bors retry

GitHub credits issue.
2025-03-05 17:32:58 137513
> The hosted runner encountered an error while running your job. (Error Type: Disconnect).

@bors retry


2025-03-05 17:03:01 137011
@bors retry
2025-03-04 12:07:08 137373
@bors retry (spurious mingw)
2025-03-04 10:08:13 137373
@bors retry
2025-03-04 08:12:46 137985
@bors retry
2025-03-03 18:24:49 137925
The rfl job is a rustup error and is getting disabled.

@bors retry
2025-03-03 16:31:53 137927
@bors retry
2025-03-03 16:13:16 137914
@bors retry
2025-03-03 13:54:04 137373
Oh... I think that might be a `rust-lld` issue where sometimes it just *dies*.

Let's see on a retry.

@bors retry
2025-03-03 11:33:25 137921
@bors retry
2025-03-03 10:39:42 137373
@bors retry

Trying again after ~30 minutes.
2025-03-03 10:10:03 137914
@bors retry
2025-03-03 10:03:31 137373
@bors p=101
@bors retry
2025-03-03 09:45:55 137373
@bors retry
2025-03-03 09:44:31 135695
@bors retry
@bors treeclosed ghcr network errors
2025-03-03 09:29:02 137914
@bors retry
2025-03-03 09:12:41 135695
@bors retry network error

sigh..
2025-03-03 08:32:59 137921
@bors retry Get "https://ghcr.io/v2/": context deadline exceeded
2025-03-03 08:32:39 135695
@bors retry network error
2025-03-03 08:29:41 137918
@bors retry spurious network error
2025-03-03 07:14:36 137914
@bors retry
2025-03-01 22:20:58 137855
 @bors retry
2025-03-01 18:12:18 137752
@bors retry
2025-03-01 05:21:59 133250
@bors retry
2025-02-28 10:56:38 137517
@bors retry
2025-02-28 10:15:01 137775
@bors retry
2025-02-28 09:50:42 137775
@bors retry
2025-02-27 12:02:40 137710
@bors retry
2025-02-27 10:54:22 137669
@bors retry
2025-02-27 10:25:58 137710
@bors retry
2025-02-27 07:43:05 137425
@bors retry for the time being 
2025-02-27 05:55:56 135695
what the fuck?????
@bors retry 
2025-02-25 07:44:16 133832
@bors retry
2025-02-25 04:52:53 136921
@bors retry
2025-02-23 20:31:26 137497
Yeah sorry meant to do that but got distracted.

@bors r- retry
2025-02-23 20:17:51 137476
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
2025-02-21 16:21:11 137189
With the switch to smaller builders, updating CI config now more often ends in timeouts :disappointed: Let's try again.

@bors retry
2025-02-21 15:00:46 136921
@bors retry
2025-02-20 22:33:42 137189
Sounds spurious.

@bors retry
2025-02-19 19:19:03 137123
@bors retry temp for failure on windows
2025-02-19 17:57:37 137023
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
2025-02-18 17:29:31 137226
@bors r- retry
2025-02-18 07:48:01 135408
@bors r- retry
There's still something wrong with `tests/codegen/abi-x86-sse.rs`.
2025-02-17 02:11:55 136804
@bors retry r- (still in the queue (unapproved ofc))
2025-02-15 22:27:51 137093
@bors retry
2025-02-15 17:59:10 137034
@bors retry
2025-02-15 06:54:08 136864
@bors retry mysql error
2025-02-14 22:18:00 136828
@bors retry (after #137041)
2025-02-14 21:46:58 136363
@bors retry (after #137041)
2025-02-14 21:31:14 137034
@bors retry
(after #137041)
2025-02-11 18:25:43 136878
@bors retry (remote-test-client spurious)
2025-02-11 02:33:56 136804
@bors retry

(Trying to poke bors into being less confused without a full resync.)
2025-02-10 08:44:23 136803
yielding once to retry the rollup of this, to see if its failure was spurious
@bors retry
2025-02-10 08:43:37 136804
@bors retry
2025-02-10 01:40:44 133092
@bors r- retry

https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/bors.20stuck.3F.20.282025-02-09.29
2025-02-09 10:09:16 136754
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
2025-02-09 02:06:58 136754
praying for spurious?

@bors retry
2025-02-08 18:31:45 136740
@bors retry
2025-02-08 11:22:48 136728
@bors retry
2025-02-08 09:13:48 136586
> 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