-
Notifications
You must be signed in to change notification settings - Fork 91
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
Segfault in test shutdown with specific module #866
Labels
Comments
mrbean-bremen
added a commit
to mrbean-bremen/pyfakefs
that referenced
this issue
Aug 17, 2023
- avoids problems with cached modules during session shutdown - see pytest-dev#866
6 tasks
mrbean-bremen
added a commit
to mrbean-bremen/pyfakefs
that referenced
this issue
Aug 18, 2023
- avoids problems with cached modules during session shutdown - see pytest-dev#866
mrbean-bremen
added a commit
to mrbean-bremen/pyfakefs
that referenced
this issue
Aug 18, 2023
- avoids problems with cached modules during session shutdown - see pytest-dev#866
mrbean-bremen
added a commit
to mrbean-bremen/pyfakefs
that referenced
this issue
Aug 18, 2023
- avoids problems with cached modules during session shutdown - see pytest-dev#866
mrbean-bremen
added a commit
that referenced
this issue
Aug 18, 2023
- avoids problems with cached modules during session shutdown - see #866
Closing as handled - shall be reopened if a similar issue comes up again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I accidentally stumbled over an issue related to pyfakefs if running it with
opentimelineio
code.With the following code (copied from the issue):
If running this, a segmentation fault occurs on test shutdown, and with Python versions >=3.10 an additional error is shown:
I can reproduce this on all systems (Windows, Linux, MacOS) in the CI, with different Python and Pytest versions (except for Python 3.7 with Pytest versions from 4.6 to 5.3, for some reason).
I currently have no idea what causes this, but is seems to have something to do with the cache.
The text was updated successfully, but these errors were encountered: