Zalathar 7cb6912f46 Remove a flaky got_timeout assert from two channel tests ...

In CI, the receiver thread can be descheduled for a surprisingly long time, so
there's no guarantee that a timeout actually occurs.

2026-03-07 21:16:00 +11:00

..

barrier.rs

Make the compile test use a const instead

2025-09-09 17:14:38 +02:00

condvar.rs

move condvar test from mutex to condvar test file

2025-10-31 15:53:39 -04:00

lazy_lock.rs

modify LazyLock poison panic message

2025-08-22 14:59:34 -04:00

lib.rs

add oneshot tests

2026-01-05 09:47:20 +11:00

mpmc.rs

Remove a flaky got_timeout assert from two channel tests

2026-03-07 21:16:00 +11:00

mpsc_sync.rs

Move std::sync unit tests to integration tests

2025-01-26 10:28:05 +00:00

mpsc.rs

Remove a flaky got_timeout assert from two channel tests

2026-03-07 21:16:00 +11:00

mutex.rs

move condvar test from mutex to condvar test file

2025-10-31 15:53:39 -04:00

once_lock.rs

Mark some std tests as requiring panic = "unwind"

2025-03-10 08:31:06 -07:00

once.rs

Mark some std tests as requiring panic = "unwind"

2025-03-10 08:31:06 -07:00

oneshot.rs

Remove two more flaky assertions from oneshot tests

2026-02-20 12:48:27 +11:00

reentrant_lock.rs

Move std::sync unit tests to integration tests

2025-01-26 10:28:05 +00:00

rwlock.rs

Implement non-poisoning Mutex::with_mut, RwLock::with and RwLock::with_mut

2025-10-04 17:16:00 +08:00