Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 33.9k
test_peg_generator and test_freeze require cpu#108386
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
vstinner commented Aug 23, 2023 • edited
Loading Uh oh!
There was an error while loading. Please reload this page.
edited
Uh oh!
There was an error while loading. Please reload this page.
The test_peg_generator and test_tools.test_freeze tests now require the 'cpu' resource. Skip these tests unless the 'cpu' resource is enabled (it is disabled by default). These tests are no longer skipped if Python is built with ASAN or MSAN sanitizer.
vstinner commented Aug 23, 2023
Comparision, total timing BEFORE => AFTER:
The exact timing depends when slowest tests are run. If slowest tests are run at the end, the difference of this PR is less. GHA jobs timing without this PRUse #108383 as reference but use #108381 for Windows x86 (since in the other PR, test_concurrent_futures was re-run!). Windows x64: macOS: Ubuntu: Address Sanitizer: GHA jobs timing with the PRWindows x86: Windows x64 (test_concurrent_futures failed and had to be re-run!): macOS: Ubuntu: Address Sanitizer: |
The test_peg_generator and test_tools.test_freeze tests now require the 'cpu' resource. Skip these tests unless the 'cpu' resource is enabled (it is disabled by default).
These tests are no longer skipped if Python is built with ASAN or MSAN sanitizer.