Skip to content

Commit

Permalink
ignore will_wake tests in Miri, their result is not fully predictable
Browse files Browse the repository at this point in the history
  • Loading branch information
RalfJung committed Aug 9, 2024
1 parent 9a233bb commit 32d3104
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions library/alloc/tests/task.rs
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ use alloc::task::{LocalWake, Wake};
use core::task::{LocalWaker, Waker};

#[test]
#[cfg_attr(miri, should_panic)] // `will_wake` doesn't guarantee that this test will work, and indeed on Miri it fails
#[cfg_attr(miri, ignore)] // `will_wake` doesn't guarantee that this test will work, and indeed on Miri it can fail
fn test_waker_will_wake_clone() {
struct NoopWaker;

Expand All @@ -20,7 +20,7 @@ fn test_waker_will_wake_clone() {
}

#[test]
#[cfg_attr(miri, should_panic)] // `will_wake` doesn't guarantee that this test will work, and indeed on Miri it fails
#[cfg_attr(miri, ignore)] // `will_wake` doesn't guarantee that this test will work, and indeed on Miri it can fail
fn test_local_waker_will_wake_clone() {
struct NoopWaker;

Expand Down

0 comments on commit 32d3104

Please sign in to comment.