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
Tests fail on 1-core machine #114
Comments
That's definitely not an expected behavior. I take it your build chain with 2 cores is passing (to eliminate possibility of it being dependency related rather than hardware)? Are you running the test suite sequentially or in parallel with other tests? If you can modify the source running uncommenting those debug lines above the stack trace might be helpful to see if it is one missed message or something more systemic. |
just re-tested and found that there are also issues with 2 and 4 cores :-(
we are on 0.4.0 - I can also try to go to 0.4.3 first. |
0.4.3 looks somewhat better. there, 2-core and 4-core runs passed and 1-core tests had just this 1 failure:
|
Also tested 0.5.0 and in 1 of 2 tries, I got the test_async_parallel_notebooks Timeout. |
test_async_parallel_notebooks has a known issue rooted in jupyter_client that is unresolved: jupyter/jupyter_client#487. Basically there's a race condition that test are sometimes loosing for port aquisition. |
While working on reproducible builds for openSUSE, I found that our
python-nbclient
package fails tests on a 1-core VMIs this a bug or expected behaviour?
jmcarpenter2/swifter#102 solved a similar issue by skipping such tests when not enough cores were available.
to reproduce on openSUSE or Debian:
The issue can also be triggered via
taskset 1 pytest-3.8
example failure log:
The text was updated successfully, but these errors were encountered: