-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
TST: Isolate Qt tests in subprocesses to fix QApplication leakage #31072
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
base: main
Are you sure you want to change the base?
Conversation
This reverts commit 5ce82b7.
timhoffm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technical note:
- Please remove all unrelated style changes. We don't want style churn and no reviewer will invest time to spot the actual logic changes in a wall trival style changes.
The PR explantion looks AI-generated. Please make sure to comply with our AI policy.
https://matplotlib.org/devdocs/devel/contribute.html#restrictions-on-generative-ai-usage
|
@timhoffm I have reverted all unrelated style changes as requested. Regarding the AI policy: Apologies for the confusion. Since this is my first open-source contribution, I was eager to ensure everything was perfect. I want to confirm that I fully understood the entire logic and wrote the fix myself. I only used AI tools to help polish my English phrasing as a non-native speaker. |
I isolated the Qt tests into subprocesses to prevent QApplication memory leaks.
Change 1. Moved Qt test logic into subprocess.run.
Change 2. Added env=os.environ to fix the DISPLAY variable error on Linux CI.
Change 3. Reverted all unrelated style changes.