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
When running the test suite generated by --enable-tests for the monad-par package, in revision 60aabe6, I see non-determinstic failures on the Direct scheduler.
Specifically, if I try to run this command 10 times:
./dist/build/test-monad-par/test-monad-par -j1
It will fail. However, the weird part is that it depends on running multiple tests together. If I run JUST the pmrr1 test, even 1000 times, I cannot reproduce the error:
This is exactly the same pattern I've seen in other projects that use test-framework to drive parallel tests, including lattice-par and haskell-lockfree -- the outcome depends on what set of tests is run. I haven't figured out WHY this is yet.
The text was updated successfully, but these errors were encountered:
When running the test suite generated by
--enable-tests
for the monad-par package, in revision 60aabe6, I see non-determinstic failures on the Direct scheduler.Specifically, if I try to run this command 10 times:
It will fail. However, the weird part is that it depends on running multiple tests together. If I run JUST the pmrr1 test, even 1000 times, I cannot reproduce the error:
This is exactly the same pattern I've seen in other projects that use test-framework to drive parallel tests, including
lattice-par
andhaskell-lockfree
-- the outcome depends on what set of tests is run. I haven't figured out WHY this is yet.The text was updated successfully, but these errors were encountered: