Crash when assert fails in multiprocessing task #1984
Comments
indeed, py.test currently expects real tracebacks, and multiprocessing is NOT supplying that |
This is affecting me really heavily - I'm trying to covert a large python2 app to python3 and this is preventing most of the suite from running. |
I noticed this only happens because of the code which tries to print chained exceptions in Python 3+. As a workaround, it is possible to use
|
That works, thanks! |
Thanks, that works! I suspect that it also happens for threading, not just On Tue, Oct 25, 2016 at 8:33 PM Bruno Oliveira notifications@github.com
|
@Daenyth could you please post the traceback you were getting? Just want to make sure you were also having the exact same problem as the OP. |
|
Thanks! |
Seems that pytest crashes when trying to get the code snippet of an assertion failure when the assertion failure occurs in a
multiprocessing
task.Here's a log of the pytest run https://gist.github.com/adborden/376f2dd3defae8fced33b655913e5f91#file-pytest_crash-log
Here's the test case that causes the crash
https://gist.github.com/adborden/376f2dd3defae8fced33b655913e5f91#file-test_pytest_crash-py
Here's a snippet of the traceback (see above for full stack).
Using pytest-3.0.3 on Ubuntu 15.10
Virtualenv:
The text was updated successfully, but these errors were encountered: