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.

Sign up for GitHub

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

Jump to bottom

current tests are not fully "deterministic" / have timing issues #4

Open

gst opened this issue Jul 31, 2015 · 0 comments

gst commented Jul 31, 2015

which can be easily triggered by running the tests under a heavy loaded system.

An easy/possible way to achieve this is to start many(sufficiently) instance of the tests in parallel :

gstarck@taf $ for x in $(seq 20)
> do
> (python setup.py test &> res$x || echo "res$x failed .." ) &
> done | grep -c failed

5
✔ ~/work/public/python/pybreaker [master|…20]
gstarck@taf $

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment