You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
sporksmith
added a commit
to sporksmith/shadow
that referenced
this issue
Jul 3, 2023
This seems to be the only reliable workaround for
<tokio-rs/loom#316>
On the bright side this lets us increase the number of threads tested in
`test_reuse_keys_after_thread_exit`
This seems to be the only reliable workaround for
<tokio-rs/loom#316>
On the bright side this lets us increase the number of threads tested in
`test_reuse_keys_after_thread_exit`
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.The text was updated successfully, but these errors were encountered: