Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test pmrr1 reveals weird (but common) pattern of non-deterministic failure. (Direct) #35

Open
rrnewton opened this issue Sep 11, 2013 · 1 comment

Comments

@rrnewton
Copy link
Collaborator

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:

./dist/build/test-monad-par/test-monad-par -j1 -t pmrr1

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.

@rrnewton
Copy link
Collaborator Author

Let's see, referring to you by name, @aturon, should bring you into this thread. This was the same problem we were having with SNZI counters right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant