{{ message }}
Fix test_regrtest when run with uops always on - #108778
Merged
Merged
Conversation
Member
Author
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
2 participants
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 fix has two parts:
-X uopsis detected, pass it on to the subprocess created to run the manufactured test.I need this so I can run
./python -Xuops -m test test_regrtestand see it fail without the next fix.-R 6:3:inArgsTestCase.test_huntrleaksinstead of-R 3:3:-- it takes longer to settle with-X uops.(This is an attempt to make gh-107820 pass all tests. The other failure there is an failing assertion in
test_exceptions, but I believe that's fixed by gh-108725.)