-
-
Notifications
You must be signed in to change notification settings - Fork 3k
testing: Explicitly pass -Werror to tests needing it
#13481
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
Conversation
Explicitly pass `-Werror` to `runpytester()` in the few additional tests needing it, in order to fix test failures when the test suite is run with `-Wdefault` or a similar override. Fixes pytest-dev#13480
|
The unraisableexception tests were handled in another PR, so this is ready to go. I tweaked the changelog a bit. |
|
Thanks! |
Backport to 8.4.x: 💚 backport PR created✅ Backport PR branch: Backported as #13538 🤖 @patchback |
testing: Explicitly pass `-Werror` to tests needing it (cherry picked from commit 667398f)
…67398f53b7ca9a19a540054b03d505b84379114/pr-13481 [PR #13481/667398f5 backport][8.4.x] testing: Explicitly pass `-Werror` to tests needing it
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to pytest-dev#13481.
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to #13481.
Since this is related only to internal testing and does not affect end-users, it is more appropriate to announce it in the "Contributor" section of the changelog. Follow up to #13481. (cherry picked from commit cc580b5) Co-authored-by: Bruno Oliveira <[email protected]>
Explicitly pass
-Werrortorunpytester()in the few additional tests needing it, in order to fix test failures when the test suite is run with-Wdefaultor a similar override.Fixes #13480
If this change fixes an issue, please:
closes #XYZWto the PR description and/or commits (whereXYZWis the issue number). See the github docs for more information.Unless your change is trivial or a small documentation fix (e.g., a typo or reword of a small section) please:
Create a new changelog file in the
changelogfolder, with a name like<ISSUE NUMBER>.<TYPE>.rst. See changelog/README.rst for details.Write sentences in the past or present tense, examples:
Also make sure to end the sentence with a
..Add yourself to
AUTHORSin alphabetical order.