Homu retry log - rust

Time (UTC) PR Message
2024-05-15 21:45:06 125157
@bors r- retry (bors seems to think this PR is approved and is not running a try-only build?)
2024-05-15 18:15:55 125157
@bors retry
2024-05-15 18:02:08 125003
@bors retry
2024-05-15 09:18:38 124975
@bors retry
2024-05-15 02:48:14 124050
@bors retry
2024-05-13 06:29:20 125055
Clearly another CI issue.

@bors retry
2024-05-13 03:15:50 125055
...failed to download tidy-html?
Let's try again.
@bors retry
2024-05-11 06:32:04 124969
>   --- stderr -------------------------------
>   thread 'main' panicked at src/tools/remote-test-client/src/main.rs:310:9:
>   client.read_exact(&mut header) failed with Connection reset by peer (os error 104)
>   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


Suspicious and not related. @bors retry
2024-05-09 13:03:25 124850
@bors retry
2024-05-09 09:35:42 124850
@bors retry
2024-05-08 17:22:06 124788
@bors retry r-
2024-05-07 13:09:45 124738
@bors retry

DNS…
2024-05-07 02:45:28 124813
@bors retry remote-test-client failure
2024-05-07 00:11:49 124738
Failed to push the docker image.

@bors retry
2024-05-06 17:38:14 124771
@bors retry
2024-05-05 01:18:35 124730
> ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled

@bors retry
2024-05-05 01:08:38 122662
@bors retry Connection reset by peer in remote-test-client
2024-05-04 15:28:06 124704
@bors retry
2024-05-04 15:26:37 124710
@bors retry
2024-05-04 00:38:06 124684
I'm not sure what caused the error.

@bors retry rollup=never p=1
2024-05-03 11:16:44 122662
@bors retry r-
2024-05-03 01:51:12 122253
> ⌛ Testing commit [ed532cc](https://github.com/rust-lang/rust/commit/ed532cc186a651a3e4b848ffbef8c080018f1732) with merge [4d96c3e](https://github.com/rust-lang/rust/commit/4d96c3efd8f1abcc82a7148c5ec0657bd486571e)...

That's a zombie.

@bors retry for good measure.
2024-05-03 01:46:39 123602
> ⌛ Testing commit [c19866f](https://github.com/rust-lang/rust/commit/c19866f335152cbdd3424b573e5a615963dbe80e) with merge [460356f](https://github.com/rust-lang/rust/commit/460356fe8b94d18fde00d2f167653e6f33513f09)...

That's a zombie.

@bors retry for good measure
2024-05-03 00:16:37 123441
@bors retry
2024-05-02 09:28:26 121848
@bors retry
2024-05-02 01:15:26 124584
@bors retry
2024-05-01 01:30:22 124491
It looks like we do in fact use the right one for the appleOS platforms: https://github.com/rust-lang/rust/blob/f705de59625bb76067a5d102edc1575ff23b8845/library/core/src/ffi/mod.rs#L207-L235

Yeah I think it was just a timeout.

@bors retry
2024-04-29 00:04:25 124498
@bors retry
2024-04-28 00:09:59 124454
@bors retry
2024-04-27 07:36:26 124370
@bors retry
2024-04-27 05:27:14 124426
@bors retry
2024-04-26 23:03:31 124416
@bors retry

Posted https://github.com/rust-lang/cargo/pull/13811 to fix the flaky test.
2024-04-26 00:09:50 124076
@bors retry yield to rollup
2024-04-26 00:07:51 124379
@bors retry
2024-04-25 17:09:37 122504
@bors retry
2024-04-24 23:42:15 123550
Looks spurious. @bors retry
2024-04-24 17:11:52 124303
@bors retry
2024-04-24 17:11:32 104087
@bors retry
2024-04-24 16:35:42 124330
For good measure: @bors retry
2024-04-24 16:23:16 104087
@bors retry
2024-04-22 22:20:37 124271
Seems flaky.

@bors retry
2024-04-22 20:20:29 104087
Another instance of https://github.com/rust-lang/rust/issues/123583.
@bors retry
2024-04-22 17:48:05 115913
Looks like a flaky test in miri, other PRs have run into that too.

@bors retry
2024-04-22 16:34:00 123992
wtf ci

@bors retry
2024-04-22 05:02:13 124236
@bors retry
2024-04-21 20:38:23 124112
Looks unrelated

@bors retry
2024-04-20 08:52:14 123409
@bors retry (flaky ci)
2024-04-20 00:30:46 124177
@bors retry

401 Unauthorized docker accessing ghcr.io 
2024-04-19 22:50:04 124177
@bors retry

#97669 armhf-gnu failed
2024-04-19 05:08:04 124123
@bors retry
2024-04-18 22:51:48 124123
@bors retry

what
2024-04-18 04:11:01 124038
@bors retry 
2024-04-17 16:02:10 123978
As long as it's not a timeout, which this doesn't appear to be, then I think we can just retry.

@bors retry
2024-04-17 14:24:02 122013
@bors retry
2024-04-16 19:53:02 123537
@bors retry
2024-04-16 09:32:35 123468
@bors retry
2024-04-16 09:32:13 123537
@bors retry
2024-04-16 04:53:22 123468
@bors retry
2024-04-16 00:09:26 123468
what the heck lol

@bors retry
2024-04-15 19:18:44 123900
@bors retry yield to rollup
2024-04-15 11:37:24 123941
@bors retry - miri reports a memory leak but I doubt it's related to this PR (#123961 for follow-up)
2024-04-15 04:52:00 122997
@bors retry
2024-04-14 18:12:05 123719
Looks like an instance of https://github.com/rust-lang/rust/issues/123583.
@bors retry
2024-04-14 13:17:08 122268
Failed in miri on i686-pc-windows-gnu. However this PR only affects msvc, aside from changing some `libc` imports to be `core::ffi` ones so it's unlikely to be caused by this PR. @rust-lang/miri 

<details><summary>i686-pc-windows-gnu miri</summary>

```  
  error: memory leaked: alloc27197638 (Rust heap, size: 8, align: 4), allocated here:
  Error:     --> /checkout/library/alloc/src/alloc.rs:100:9
       |
  100  |         __rust_alloc(layout.size(), layout.align())
       |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       |
       = note: BACKTRACE:
       = note: inside `realstd::alloc::alloc` at /checkout/library/alloc/src/alloc.rs:100:9: 100:52
       = note: inside `realstd::alloc::Global::alloc_impl` at /checkout/library/alloc/src/alloc.rs:183:73: 183:86
       = note: inside `<realstd::alloc::Global as core::alloc::Allocator>::allocate` at /checkout/library/alloc/src/alloc.rs:243:9: 243:39
       = note: inside `alloc_crate::alloc::exchange_malloc` at /checkout/library/alloc/src/alloc.rs:332:11: 332:34
       = note: inside `realstd::boxed::Box::<realstd::sys::thread_local::os_local::Value<u8>>::new` at /checkout/library/alloc/src/boxed.rs:218:9: 218:20
       = note: inside `realstd::thread::local_impl::Key::<u8>::try_initialize::<{closure@/checkout/library/std/src/sys/thread_local/os_local.rs:28:27: 28:34}>` at /checkout/library/std/src/sys/thread_local/os_local.rs:145:37: 145:94
       = note: inside `realstd::thread::local_impl::Key::<u8>::get::<{closure@/checkout/library/std/src/sys/thread_local/os_local.rs:28:27: 28:34}>` at /checkout/library/std/src/sys/thread_local/os_local.rs:127:18: 127:43
  note: inside `sync::reentrant_lock::current_thread_unique_ptr::X::__getit`
      --> /checkout/library/std/src/sys/thread_local/os_local.rs:28:17
       |
  11   |   pub macro thread_local_inner {
       |   ----------------------------
       |   |
       |   in this expansion of `$crate::thread::local_impl::thread_local_inner!` (#2)
       |   in this expansion of `$crate::thread::local_impl::thread_local_inner!` (#3)
  ...
  28   | /                 __KEY.get(move || {
  29   | |                     if let $crate::option::Option::Some(init) = _init {
  30   | |                         if let $crate::option::Option::Some(value) = init.take() {
  187 | |     () => {};
  ...   |
  195 | |         $crate::thread::local_impl::thread_local_inner!($(#[$attr])* $vis $name, $t, const $init);
      | |         ----------------------------------------------------------------------------------------- in this macro invocation (#2)
  ...   |
  207 | |     );
  208 | | }
      | |_- in this expansion of `thread_local!` (#1)
      = note: inside `realstd::thread::LocalKey::<u8>::try_with::<{closure@library/std/src/sync/reentrant_lock.rs:319:12: 319:15}, usize>` at /checkout/library/std/src/thread/local.rs:285:37: 285:55
      = note: inside `realstd::thread::LocalKey::<u8>::with::<{closure@library/std/src/sync/reentrant_lock.rs:319:12: 319:15}, usize>` at /checkout/library/std/src/thread/local.rs:262:9: 262:25
  note: inside `sync::reentrant_lock::current_thread_unique_ptr`
     --> library/std/src/sync/reentrant_lock.rs:319:5
      |
  319 |     X.with(|x| <*const _>::addr(x))
      |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  note: inside `sync::reentrant_lock::ReentrantLock::<()>::try_lock`
     --> library/std/src/sync/reentrant_lock.rs:226:27
      |
  226 |         let this_thread = current_thread_unique_ptr();
      |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  note: inside closure
     --> library/std/src/sync/reentrant_lock/tests.rs:47:20
      |
  47  |         let lock = l2.try_lock();
      |                    ^^^^^^^^^^^^^
```

</details>

@bors retry miri i686-pc-windows-gnu std
2024-04-14 08:53:34 123719
@bors retry "   Error: The operation was canceled."
2024-04-13 03:05:40 123257
Seems spurious, considering this PR doesn't affect Linux

@bors retry
2024-04-13 02:39:31 123874
Seems irrelevant to cargo

@bors retry
2024-04-12 00:04:24 123801
@bors retry
2024-04-11 01:37:56 122213
@bors retry
2024-04-11 01:36:37 123007
@bors retry
2024-04-11 00:33:54 122470
@bors retry yield to a rollup
2024-04-11 00:33:39 123762
@bors retry
2024-04-11 00:26:51 122470
🤔 
CI failure?

@bors retry
2024-04-10 14:24:19 121346
@bors retry
2024-04-09 20:14:03 123682
@bors retry
2024-04-09 17:18:34 123682
Backported a fix for the tidy issue we saw in https://github.com/rust-lang/rust/pull/123681#issuecomment-2045723120.

@bors retry r+ p=500 rollup=never
2024-04-09 17:07:47 122918
@bors retry

Yielding priority to the stable release.
2024-04-05 15:47:17 123466
@raoulstrackx those tests do run in the `test-various` job -- [here](https://github.com/rust-lang-ci/rust/actions/runs/8566085241/job/23475198435#step:27:27372) it is in the most recent logs. Search for "suite=assembly" if that link doesn't take you to the right line. They also pass in my local build. I wonder what's different in your CI?

---

Not sure why bors didn't react to CI completion here -- let's have another go...

@bors retry
2024-04-04 09:05:24 123356
I can reproduce the miri issue without this change. I have a working theory, but I'll see if I can minimize the example first.

As it's an unrelated failure, it's not blocking this PR.
@bors retry
2024-04-04 00:28:27 123052
@bors retry
2024-04-04 00:07:53 123240
@bors retry
2024-04-03 00:03:42 122791
@bors retry