Merged
Conversation
The test was throwing import errors past the lifetime of the owning scoped_interpreter
henryiii
approved these changes
Jul 27, 2025
Collaborator
|
@b-pass There was this flake again (resolved by a rerun): https://github.com/pybind/pybind11/actions/runs/16509608392/job/46688698596?pr=5768 For context, from a little further up in the log: I.e. similar to what I saw (and reported elsewhere) before, this is with Python 3.12. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The test was throwing import errors past the lifetime of the owning scoped_interpreter
Description
The test was supposed to import a test module, but because it is "isolated", the path is not set, so the module cannot be imported. A
ModuleNotFounderror is thrown, but not caught, and then propagates past thescoped_interpreterwhich owns it.The stack of the SEGV doesn't point to the test itself, so it was difficult to track down:
I do not really understand how this passes as it is.
@rwgk this is what I found when investigating the flake from #5766. I don't know if this is the actual cause....
Suggested changelog entry: