You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug TestExceptionInfo.test_traceback_not_referenced fails when the test suite is run using PyPy3:
_________________________________________________TestExceptionInfo.test_traceback_not_referenced_________________________________________________self=<test_errors.TestExceptionInfoobjectat0x00007fb05c3fbb40>deftest_traceback_not_referenced(self):
""" Ensure that an ExceptionInfo does not keep a reference to the traceback, as doing so can create unintended side effects. See #386 for more info. """state=mock.MagicMock()
_=errors.ExceptionInfo(None, None, DeletionDetector(state))
>assertstate.deletedEAssertionError: assertFalseE+whereFalse=<MagicMockid='140395438949168'>.deletedtests/test_errors.py:24: AssertionError
To Reproduce
Steps to reproduce the behavior:
Install dependencies for pypy3 (tox doesn't seem to work here, I used distribution packages)
This finding was a surprise to me. So it seems that neither black no mypy install on pypy (due to python/typed_ast#111). I've reached out to the typing team on gitter to see how permanent that condition is.
Describe the bug
TestExceptionInfo.test_traceback_not_referenced
fails when the test suite is run using PyPy3:To Reproduce
Steps to reproduce the behavior:
tox
doesn't seem to work here, I used distribution packages)pypy3 -m pytest
Expected behavior
All tests passing.
Environment
Run from git master (fb74a37).
Additional context
My guess would be that it's due to different GC behavior in PyPy.
The text was updated successfully, but these errors were encountered: