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 |
2024-03-31 16:03:49 |
121851 |
@bors retry |
2024-03-30 14:18:36 |
123207 |
likely indeed
@bors retry |
2024-03-28 22:25:40 |
122671 |
@bors retry since the failure was spurious |
2024-03-28 22:12:21 |
123080 |
@bors retry |
2024-03-28 21:59:02 |
123071 |
@bors retry |
2024-03-28 21:49:44 |
120557 |
you're fine
@bors retry https://github.com/rust-lang/rust/pull/122671#issuecomment-2026178791 |
2024-03-28 21:49:29 |
122616 |
@bors retry https://github.com/rust-lang/rust/pull/122671#issuecomment-2026178791 |
2024-03-28 21:49:14 |
122975 |
@bors retry https://github.com/rust-lang/rust/pull/122671#issuecomment-2026178791 |
2024-03-28 21:48:54 |
123172 |
@bors retry https://github.com/rust-lang/rust/pull/122671#issuecomment-2026178791 |
2024-03-27 13:19:04 |
123117 |
@bors retry
```
unable to access 'https://github.com/rust-lang-ci/rust/': Failed to connect to github.com port 443 after 75011 ms: Couldn't connect to server
``` |
2024-03-27 01:18:01 |
123105 |
@bors retry
#97669 armhf-gnu issue |
2024-03-26 06:45:37 |
123081 |
@bors retry |
2024-03-26 00:49:04 |
123065 |
@bors retry |
2024-03-25 08:54:02 |
123027 |
@bors retry |
2024-03-24 20:35:20 |
123010 |
@bors retry |
2024-03-24 14:51:45 |
122658 |
@bors retry apple-aarch64 timed out |
2024-03-24 04:48:12 |
121940 |
Looks like a network issue.
@bors retry |
2024-03-23 21:12:41 |
122959 |
@bors retry |
2024-03-23 13:42:48 |
122582 |
@bors retry |
2024-03-22 21:04:11 |
122900 |
@bors retry
https://github.com/rust-lang/rust/pulls?q=is%3Apr+%22+cannot+find+value+%60missing_ident%60%22+ |
2024-03-22 16:54:04 |
121940 |
@bors retry |
2024-03-22 09:47:15 |
119552 |
the failure may be spurious
@bors retry |
2024-03-22 03:07:38 |
122370 |
@bors retry |
2024-03-22 01:01:02 |
122846 |
@bors retry |
2024-03-19 17:26:04 |
122029 |
@bors retry |
2024-03-18 21:25:56 |
122693 |
@bors retry yield rollup |
2024-03-18 09:24:12 |
122558 |
@bors retry |
2024-03-17 19:46:04 |
121952 |
Seems spurious?
@bors retry |
2024-03-17 11:52:03 |
122628 |
Huh
@bors retry |
2024-03-16 23:53:51 |
122574 |
"Connection reset" in remote-test-client
@bors retry |
2024-03-16 00:20:39 |
121926 |
@bors retry |
2024-03-15 00:06:51 |
122517 |
@bors retry The runner has received a shutdown signal |
2024-03-14 06:30:03 |
122243 |
@bors retry timeout |
2024-03-14 03:35:07 |
122454 |
@bors retry |
2024-03-13 18:05:40 |
122444 |
@bors retry |