Homu retry log - rust

Time (UTC) PR Message
2025-05-07 19:51:34 140751
Seems flaky, let's retry.

@bors retry x86_64-mingw-2
2025-05-07 14:53:54 140727

@bors retry 

(msvc job couldn’t create temp dir)

https://github.com/rust-lang/rust/pull/132675#issuecomment-2466664810

2025-05-06 19:26:37 140514
@bors rollup retry
2025-05-02 04:25:47 140540
[The CI job “succeeded” hours ago](https://github.com/rust-lang-ci/rust/actions/runs/14782882110/job/41512999598), but bors seems to be stuck thinking it's still running.

@bors retry
2025-05-01 10:52:33 137762
@bors retry r-
2025-05-01 06:40:38 139965
@bors retry #97669
2025-04-30 20:41:13 140528
@bors retry r-
2025-04-28 15:11:02 140388
spurious 

@bors retry x86_64-mingw-1 0xc0000374
2025-04-28 05:37:55 123239
@bors retry
2025-04-28 02:00:07 140377
@bors r-
@bors retry
2025-04-28 01:31:11 140376
@bors retry
2025-04-27 16:50:17 123239
CI error is unrelated to this PR. Seems spurious.

@bors retry 
2025-04-27 01:44:27 139646
@bors retry

put this in a rollup five minutes too late
2025-04-26 16:00:05 140269
*sigh* that's a completely unrelated failure

@bors retry (mingw) error: linking with `rust-lld` failed: exit code: 0xc0000374
2025-04-26 14:08:40 140269
@bors retry couldn't create a temp dir: Access is denied

If this continues to be a pain then you could try to see about backporting c07054bdd1f8927fef5b1665debff9cb27452cc0. Though hopefully that won't be necessary...
2025-04-26 10:25:42 140269
@bors retry
2025-04-25 06:08:50 140273
@bors retry
2025-04-25 04:49:29 140233
@bors retry (msvc; couldn't create a temp dir)
2025-04-25 01:26:52 140233
@bors retry rust-lld heap corruption
2025-04-23 12:13:40 140180
@bors retry The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is cancelled.
2025-04-23 11:25:56 139998
```
2025-04-23T11:21:31.7487080Z error: couldn't create a temp dir: Access is denied. (os error 5) at path "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustcvYNGC6"
2025-04-23T11:21:31.7487640Z 
2025-04-23T11:21:31.7487822Z error: aborting due to 1 previous error
```

@bors retry
2025-04-23 09:43:59 140180
@bors retry couldn't create a temp dir: Access is denied
2025-04-23 03:13:21 140180
@bors retry
2025-04-23 01:45:24 139700
@bors retry
2025-04-22 20:42:43 140165
@bors retry spurious linking with `rust-lld` failed: exit code: 0xc0000374
2025-04-21 16:13:03 140112
@bors r- retry (#140091 might mask real issues)
2025-04-21 08:09:19 140096
@bors retry
2025-04-21 06:07:31 138591
@bors retry spurious Windows error
2025-04-21 03:35:33 140096
@bors retry
2025-04-20 21:59:35 139727
```
failed to remove and recreate output directory `/Users/runner/work/rust/rust/build/x86_64-apple-darwin/test/mir-opt/strip_debuginfo`: Directory not empty (os error 66)
```
Seems spurious, and no bumped deps seem relevant
@bors retry
2025-04-20 21:24:27 140079
I could be wrong but that looks spurious to me. None of the PRs should cause librustc_driver not to be found when documenting stage 2. Let's try again

@bors retry Library not loaded: @rpath/librustc_driver-083a5cd6fc07d78e.dylib
2025-04-20 15:39:36 140021
spurious

@bors retry
2025-04-20 15:39:25 140079
@bors retry failed to remove and recreate output directory 
2025-04-20 01:12:22 140043
@bors retry network error
2025-04-19 21:02:08 140043
seems spurious

@bors retry couldn't create a temp dir: Access is denied
2025-04-19 08:11:29 140017
@bors retry
` failed to remove and recreate output directory `C:\a\rust\rust\build\x86_64-pc-windows-msvc\test\mir-opt\strip_debuginfo`: Access is denied. (os error 5)
2025-04-19 07:19:50 139114
@bors retry
2025-04-19 05:42:52 140017
@bors retry
2025-04-18 19:36:18 139114
@bors retry
```
2025-04-18T19:12:34.8633667Z    Compiling foo v0.1.0 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\tmp\cit\t245\foo)
2025-04-18T19:12:34.8634860Z    Compiling bar v0.1.0 (D:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\tmp\cit\t245\foo\bar)
2025-04-18T19:12:34.8636135Z error: couldn't create a temp dir: Access is denied. (os error 5) at path "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\rustccfrkMc"
2025-04-18T19:12:34.8636837Z
2025-04-18T19:12:34.8637137Z error: could not compile `foo` (bin "foo") due to 1 previous error

``
2025-04-18 11:23:50 139114
@bors retry
2025-04-18 10:47:30 139996
@bors retry
2025-04-18 06:37:45 139997
@bors retry
2025-04-18 06:37:25 139996
@bors retry
2025-04-18 06:04:20 139114
@bors retry
2025-04-17 21:41:41 139980
@bors retry
2025-04-16 15:35:05 139912
@bors retry
2025-04-16 06:42:13 139888
@bors retry
2025-04-15 05:06:18 139838
@bors retry
2025-04-15 04:34:15 139826
@bors retry
2025-04-15 02:46:31 139632
Yet another flaky temp dir failure.

@bors retry
2025-04-13 05:48:43 138972
```
2025-04-13T03:57:03.7507822Z thread 'main' panicked at src/tools/remote-test-client/src/main.rs:309:9:
2025-04-13T03:57:03.7509260Z client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
2025-04-13T03:57:03.7510193Z note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```

@bors retry
2025-04-13 02:59:49 139724
couldn't create a temp dir

@bors retry
2025-04-12 04:27:26 139625
> error: couldn't create a temp dir: Access is denied.

@bors retry
2025-04-11 04:35:11 139453
@bors retry
2025-04-09 14:47:12 139573
@bors retry
2025-04-09 14:46:58 139573
@bors retry mingw failed as usual 
2025-04-09 14:46:05 139581
@bors retry
2025-04-09 12:53:15 139573
@bors retry

added to the rollup
2025-04-08 23:05:02 139552
Spurious perm error.
@bors retry
2025-04-08 21:02:16 139536
@bors retry
2025-04-08 07:58:36 139474
Thank you bors, I noticed.
@bors retry
2025-04-08 04:00:31 139499
@bors retry  

closed the overlapping rollup 
2025-04-08 02:58:24 139499
@bors retry
2025-04-07 14:27:52 139463
@bors retry
https://github.com/rust-lang/rust/issues/137938 rust-lld fails with 0xc0000374
2025-04-07 03:21:53 139460
> (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)

Given this, and the fact that this failed relatively early, I'm going to retry and cross my fingers:

@bors retry
2025-04-07 02:49:46 139279
I suspect this is not spurious, but giving it a retry
@bors retry
2025-04-06 07:26:38 139414
That failure seems bogus.

@bors retry
2025-04-03 09:03:37 139301
@bors retry
2025-03-31 22:20:23 139185
@bors retry

2025-03-31 20:35:00 139182
@bors retry 
2025-03-31 12:33:51 138749
netwotk problems @bors retry
2025-03-30 03:42:28 139000
ugh race condition @bors r- retry
2025-03-29 06:15:07 139067
@bors retry
2025-03-28 15:21:29 139054
@bors retry
2025-03-28 14:43:51 138745
@bors retry
2025-03-28 12:50:39 138478
This is the same failure as the previous time (maybe due to OOM?), but let's try again.
@bors retry
2025-03-28 03:22:49 138478
Seems unrelated to this PR.

@bors retry
2025-03-28 03:22:38 139037
looks spurious

@bors retry