Homu retry log - rust

Time (UTC) PR Message
2024-07-26 20:31:17 128237
@bors retry

link.exe fun
2024-07-26 02:35:19 128216
@bors retry
2024-07-25 07:51:57 127799
@bors retry

Spurious Windows error.
2024-07-24 16:51:00 124895
@bors retry

link.exe cannot open, #127883 possibly
2024-07-23 22:36:36 126024
Flake

@bors retry
2024-07-23 20:26:30 127524
@bors retry
2024-07-23 07:36:44 127755
Yes, looks like a network error.
@bors retry
2024-07-23 07:31:19 127995
@bors retry spurious msvc error 
2024-07-22 16:37:05 127755
@bors retry
2024-07-22 13:45:58 128041
Due to that rwlock unsoundness it seems

@bors retry
2024-07-21 23:35:00 128031
@bors retry

> 2024-07-21T21:11:03.7302971Z   = 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-4206913879fae405.exe'
2024-07-21 23:01:40 128039
@bors retry ?
2024-07-21 20:23:39 128039
@bors retry
2024-07-21 19:26:51 128031
```

warning: unused import: `cargo_test_support::registry::RegistryBuilder`
 --> tests\testsuite\open_namespaces.rs:3:5
  |
3 | use cargo_test_support::registry::RegistryBuilder;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

warning: unused import: `cargo_test_support::compare::assert_e2e`
 --> tests\testsuite\profile_trim_paths.rs:4:5
  |
4 | use cargo_test_support::compare::assert_e2e;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[RUSTC-TIMING] cargo test:false 18.781
error: failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage2-tools\x86_64-pc-windows-msvc\release\cargo.exe`

Caused by:
  Access is denied. (os error 5)
warning: build failed, waiting for other jobs to finish...
```

@bors retry -- windows filesystem error, seems likely to be https://github.com/rust-lang/rust/issues/127883
2024-07-21 15:47:10 120812
@bors retry -- yielding to stable release
2024-07-21 15:46:41 128032
@bors retry  -- hopefully spurious link failure? I think I've heard something about these recently...

LINK : fatal error LNK1104: cannot open file 'C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\release\deps\miri-bdcbed7500be44cb.exe'
2024-07-21 11:16:22 127140
@bors retry failed to remove windows file
2024-07-21 03:05:25 128021
Some of these already merged.

@bors r- retry
2024-07-20 20:02:11 128011
@bors retry
2024-07-20 06:46:16 127998
@bors retry
2024-07-19 01:29:41 125915
Job is still going according to GH

@bors r- retry
2024-07-19 01:28:59 127936
Looks like there are a few things going weird https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Bors.20wants.20vacation

@bors r- retry
2024-07-19 01:17:50 127936
@bors retry
2024-07-18 10:20:44 125915
@bors retry
```
error: rustdoc failed!
status: exit code: 0xc0000005
command: ...
stderr: none
```

doesn't look particularly informative and nothing in that test uses anything const generics related
2024-07-18 03:42:38 127153
@bors r- retry
2024-07-17 19:33:11 127865
@bors retry
2024-07-17 15:54:21 127865
@bors retry 
2024-07-17 11:15:10 127851
@bors retry I'm not sure what happened to the apple builder, it just kinda stopped part way through?
2024-07-17 09:21:51 127003
Apparently the magic is

@bors r- retry
2024-07-16 16:32:04 127811
Doesn't look relevant.

@bors retry
2024-07-16 08:21:08 127693
@bors retry (aarch64-apple ci runner died?)
2024-07-15 06:04:38 127265
@bors retry LINK cannot open a file
2024-07-13 18:18:01 127558
@bors retry
2024-07-11 20:57:19 127614
@bors retry
2024-07-11 07:40:26 126777
linker error

@bors retry
2024-07-10 19:40:59 122049
@bors retry
2024-07-08 23:46:51 127001
@bors retry
2024-07-08 05:50:33 127140
@bors retry failed to remove windows file
2024-07-07 21:31:27 127140
@bors retry failed to remove windows file
2024-07-07 14:15:21 127455
@bors retry hello, bump
2024-07-07 11:37:20 127140
@bors retry ` error: failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-std\x86_64-pc-windows-msvc\release\deps\libcompiler_builtins-86bc7a5c308aedf8.rlib``
2024-07-06 16:03:48 127377
@bors retry
2024-07-06 13:40:08 127377
@bors retry
2024-07-04 15:04:37 127317
Looks unrelated
@bors retry error: failed to remove file `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage2-tools\x86_64-pc-windows-msvc\release\cargo.exe`
2024-07-03 23:53:56 127195
@bors retry
2024-07-03 18:16:29 127008
@bors retry
2024-07-03 06:26:22 127008
@bors retry
2024-07-03 00:32:28 126792
@bors retry

miri.exe`: The process cannot access the file because it is being used by another process.
2024-07-02 18:49:01 127244
@bors retry p=10
2024-07-02 15:21:38 127232
@bors retry
2024-07-02 14:08:58 127036
@bors retry
2024-07-02 13:49:39 127232
These spurious failures are really starting to compound...

@bors retry
2024-07-02 12:52:18 127232
@bors retry

(Just trying if it was perhaps trainsient Docker issue..)
2024-07-02 10:54:37 127232
@bors retry
2024-07-02 03:28:26 127136
@bors retry
2024-07-02 03:15:13 127008
@bors retry
2024-07-02 03:02:40 126171
@bors retry
2024-07-02 03:02:23 127050
@bors retry
2024-07-02 03:02:13 127168
@bors retry
2024-07-02 03:02:07 127190
@bors retry
2024-07-02 02:58:59 127127
No way this caused that.

@bors retry
2024-07-02 02:53:43 127008
@bors retry
2024-07-02 02:53:24 127136
@bors retry
2024-07-01 19:44:11 126941
@bors retry
2024-07-01 14:09:07 126880
Spurious Windows issue, probably.

@bors retry
2024-06-30 20:21:02 127026
>   thread 'main' panicked at src/lib.rs:1668:17:
  failed to copy `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\release\miri.exe` to `C:\a\rust\rust\build\x86_64-pc-windows-msvc\stage1-tools-bin\miri.exe`: The process cannot access the file because it is being used by another process. (os error 32)

https://github.com/rust-lang/rust/issues/127126 @bors retry
2024-06-30 19:03:48 127174
@bors retry
2024-06-30 16:23:01 127169
@bors retry
2024-06-30 11:09:55 127156
@bors retry
2024-06-30 09:42:33 127024
@bors retry 
2024-06-30 07:31:02 127024
Spurious error.

@bors retry
2024-06-30 01:18:15 127133
@bors retry
2024-06-29 17:51:31 120639
Test failure looks unrelated.

@bors retry
2024-06-29 05:57:31 126698
Hmm, that *looks* spurious.

@bors retry
2024-06-29 04:15:58 127096
@bors retry
2024-06-28 23:43:45 127096
@bors retry
2024-06-28 15:08:35 127066
@bors retry
2024-06-28 09:29:30 127066
@bors retry
2024-06-28 06:34:30 127000
@bors retry ?
2024-06-28 06:24:03 127066
@bors retry
2024-06-28 00:30:55 127056
@bors retry probably spurious
2024-06-26 07:21:33 125016
@bors retry r-
2024-06-25 21:54:23 126955
Same error @workingjubilee saw in the previous run. Trying once more just in case.

@bors retry
2024-06-25 19:32:28 126951
@bors retry
2024-06-25 19:12:30 126955
@bors retry
2024-06-25 18:59:10 126955
@bors retry

`Could not resolve host: github.com`
2024-06-25 18:26:43 126951
@bors retry
2024-06-25 09:32:23 126834
@bors retry spurious network issue
2024-06-24 15:55:35 126810
?

@bors retry
2024-06-24 13:43:01 126852
@bors retry
2024-06-24 08:20:39 126829
@bors retry r=workingjubilee
2024-06-23 17:10:32 126867
@bors retry
2024-06-22 01:40:24 124101
@bors retry
2024-06-21 21:31:08 126758
@bors retry
2024-06-19 13:40:15 126192
@bors retry r-
2024-06-19 13:39:41 125766
@bors retry r-
2024-06-19 13:39:12 125447
@bors retry r-
2024-06-16 21:18:38 126543
@bors retry
2024-06-16 08:57:05 126192
@bors retry
2024-06-14 21:43:23 126486
@bors retry no logs