I've found that --test-threads 1, or disabling one of the tests test_reuse_keys_after_thread_exit or test_get_and_remove_threaded also suppresses the crash; it seems like some concurrency or resource issue inside loom? I don't think these tests share any global state in my own code that would cause them to interact.
Panic at loom-0.6.0/src/rt/scheduler.rs:134:48:
I get this crash at this commit in my own code, with
NTHREADS
at this line set to 3 or more: https://github.com/shadow/shadow/pull/3063/files#diff-fc1070fc17824d4f886ddf84ded2d1cdcf42dd2b26552cdb0d5dd1d38ad98025R166 .I've found that
--test-threads 1
, or disabling one of the teststest_reuse_keys_after_thread_exit
ortest_get_and_remove_threaded
also suppresses the crash; it seems like some concurrency or resource issue inside loom? I don't think these tests share any global state in my own code that would cause them to interact.