-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Properly clear exceptions after test #187
Comments
fabioz
added a commit
to fabioz/pytest-qt
that referenced
this issue
Sep 24, 2017
Clearing the exceptions found during a test is needed to allow variables to be properly cleared. Fixes pytest-dev#187
nicoddemus
added a commit
to fabioz/pytest-qt
that referenced
this issue
Sep 25, 2017
Unfortunately at this moment this is still failing because of pytest-dev/pytest#2798, we will need to fix this in pytest first before being able to merge this.
Is this fixed now? |
Oh yeah, thanks for the ping. I have fixed the problem in pytest, we should be able to produce a proper test now. |
nicoddemus
pushed a commit
to fabioz/pytest-qt
that referenced
this issue
Jul 12, 2018
Clearing the exceptions found during a test is needed to allow variables to be properly cleared. Fixes pytest-dev#187
nicoddemus
added a commit
to fabioz/pytest-qt
that referenced
this issue
Jul 12, 2018
Unfortunately at this moment this is still failing because of pytest-dev/pytest#2798, we will need to fix this in pytest first before being able to merge this.
Thanks @fabioz, and sorry for the delay! |
No problems. Thanks for the fix ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an exception is thrown and is captured by pytestqt, it's keep alive (found it while trying to discover why PySide was crashing on the process exit when a test failed -- the reason was that pytestqt was keeping variables alive longer than it should and variables weren't cleared in the proper order because of that).
Will provide a fix shortly.
The text was updated successfully, but these errors were encountered: