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
v3.1.2 - test suite "frozen" after it finishes #15960
Comments
I have seen this occasionally locally but have not been able to track it down |
i can reproduce it every time i run the test suite on my development box and in a clean chroot (where we build the packages for upload). let me know what i can do to help triage this |
That is both reassuring and disappointing. My knee-jerk reaction is that it is one of the tests where we spawn a subprocess that does not close down cleanly. Can you look at the running processes when it is hung? |
this is the
so i guess that |
any idea what to look next? we cant release the new package to debian until we fix this, and the pending update contains some important fixes people are waiting for. the alternative is to skip entirely (and temporarily) the test suite, but it's really a last resort option thanks :) |
I just had the same problem in a plain
and still hanging, so another Ctrl+C:
|
Maybe #16126 is the cause? |
I didn't experience the freeze recently, so assuming fixed by #16126. |
Hello,
i'm preparing 3.1.2 for upload to Debian but i noticed something unusual: the test suite just stops when it finishes, and that blocks the execution of further build steps for Debian.
we run the tests like:
/usr/bin/xvfb-run -a python3.7 tests.py --no-network --verbose --full-trace
(exporting PYTHONPATH and MATPLOTLIBDATA accordingly)
the suite runs:
and then it just sits there forever.
is this a known issue? any idea how to debug/fix it? thanks!
The text was updated successfully, but these errors were encountered: