Homu retry log - rust

Time (UTC) PR Message
2025-07-12 04:39:59 143766
@bors retry r-
2025-07-11 09:31:22 143766
@bors retry
2025-07-11 01:09:07 143760
> The hosted runner lost communication with the server.

@bors retry
2025-07-08 21:21:42 140525
@bors retry spurious network error
2025-07-08 17:25:00 143627
@bors r- retry
2025-07-08 14:28:29 143627
@bors retry
2025-07-08 11:08:42 143627
@bors retry
2025-07-06 02:36:44 143507
@bors retry
2025-07-05 17:33:58 143478
@bors retry thread '[ui] tests/ui/rust-2018/removing-extern-crate-malformed-cfg.rs' panicked at src/tools/compiletest/src/runtest.rs:1921:47:

no idea what is up with that test...
2025-06-30 01:47:29 142941
spurious?

@bors retry
2025-06-29 13:23:37 143137
@bors retry tests\run-make\short-ice spurious failure
2025-06-28 17:50:26 143137
@bors retry r-
https://github.com/rust-lang/rust/pull/143148#issuecomment-3015902617
2025-06-28 10:15:40 141759
looks like its stuck
@bors retry r-
2025-06-28 10:14:13 142036
![image](https://github.com/user-attachments/assets/1ed2cba0-f394-42af-8ed0-b48106df5eb6)
:thinking: 
@bors retry r-
2025-06-26 17:03:41 143057
Yielding to https://github.com/rust-lang/rust/pull/142774
@bors retry
2025-06-26 07:44:56 142774
@bors retry
2025-06-26 05:24:12 141899
@bors retry

Seems like short-ice might be flaky on Windows?
2025-06-23 06:38:10 142792
The Cargo PR merged

@bors retry
2025-06-20 20:25:40 142794
I learned on Zulip that you can see this is just a runner fluke https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/molasses.20dist-x86_64-musl.20try-build/near/525099247

@bors retry
2025-06-20 05:30:18 142286
Looks like some spurious Windows file path error..

@bors retry
2025-06-14 02:08:54 142447
@bors retry
2025-06-12 19:53:23 142422
@bors retry
2025-06-12 19:52:54 142432
 @bors retry
2025-06-12 18:15:56 141491
@bors retry
2025-06-12 16:16:09 142353
@bors retry
added to #142421 
2025-06-10 10:31:54 142260
@bors r- retry
I'll ge-do the sync to include some more changes.
2025-06-10 02:12:21 142109
@bors retry

Cargo change should not affect this part of code 

https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/test-various.20failures
2025-06-10 02:12:10 142109
@bors retry

I do not know what those sanitizer errors are about. Cargo should have no effect on those tests (it isn't used), and the job doesn't set download-rustc. The image hasn't changed since the last successful build. 🤷 
2025-06-09 20:32:26 142109
@bors retry
2025-06-09 13:12:58 138062
Wut?
@bors retry
2025-06-09 09:24:31 141001
@bors retry "can't find crate for `std`" `download-ci-rustc` issue
2025-06-09 08:38:36 138062
@bors retry run-make/export/compile-interface-error: can't find crate for `std`
2025-06-08 05:32:10 130887
This failed the run-make tests?!?  That's weird...

@bors retry 
2025-06-06 11:53:13 142099
@bors retry r-
2025-06-06 05:29:25 142099
@bors retry
2025-06-05 07:03:50 135054
@bors retry
2025-06-03 07:59:04 141881
@bors retry dunno, "can't find crate for `std`"
2025-06-01 15:00:50 141745
@bors retry
yield to fixing PR CI: https://github.com/rust-lang/rust/pull/141860#issuecomment-2927367549
2025-06-01 14:28:37 141851
@bors r- retry
Needs another patch