Repository navigation
Avoid triggering module-level __getattr__ during mutation analysis - #152
Merged
LuKrO2011 merged 1 commit intoOct 24, 2026
Merged
Conversation
Mutation analysis called hasattr() on the module under test when creating the mutation controller (inspect.getsource -> hasattr(module, "__wrapped__")) and when creating each mutant (hasattr(original_module, "__path__")). For a module with a module-level __getattr__ (PEP 562), e.g., calendar on Python 3.12+, this ran the instrumented __getattr__ outside of a test execution. The tracer raised TracingAbortedException, the worker died, and after a full search the restarted worker had no time left, so no tests were written. Create the mutation controller with the tracer temporarily disabled and read the package-context attributes from the module's namespace instead.
Member
|
Hi, |
Contributor
Author
|
ok, sure, if you need any help, just comment |
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.
Mutation analysis called hasattr() on the module under test when creating the mutation controller (inspect.getsource -> hasattr(module, "wrapped")) and when creating each mutant (hasattr(original_module, "path")). For a module with a module-level getattr (PEP 562), e.g., calendar on Python 3.12+, this ran the instrumented getattr outside of a test execution. The tracer raised TracingAbortedException, the worker died, and after a full search the restarted worker had no time left, so no tests were written.
Create the mutation controller with the tracer temporarily disabled and read the package-context attributes from the module's namespace instead.