Skip to content

[3.12] gh-128770: raise warnings as errors in test suite - except for test_s… #131824

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

Closed
wants to merge 6 commits into from

Conversation

graingert
Copy link
Contributor

@graingert graingert commented Mar 28, 2025

…ocket which still logs warnings, and internal test warnings that are now logged (#128973)

Co-authored-by: Bénédikt Tran [email protected]
(cherry picked from commit 8a00c9a)

…test_socket which still logs warnings, and internal test warnings that are now logged (python#128973)

Co-authored-by: Bénédikt Tran <[email protected]>
(cherry picked from commit 8a00c9a)
@graingert graingert changed the title gh-128770: raise warnings as errors in test suite - except for test_s… [3.12] gh-128770: raise warnings as errors in test suite - except for test_s… Mar 28, 2025
@graingert graingert marked this pull request as ready for review March 28, 2025 08:57
@graingert graingert requested a review from hugovk March 28, 2025 08:58
@rhettinger rhettinger removed their request for review March 28, 2025 21:24
@python-cla-bot
Copy link

python-cla-bot bot commented Apr 6, 2025

All commit authors signed the Contributor License Agreement.

CLA signed

@Yhg1s
Copy link
Member

Yhg1s commented Apr 8, 2025

Let's not do this in 3.12 at this point. The next release is the last bugfix release, the value of surfacing warnings is mostly in the long term (making sure future changes don't introduce new warnings), and this has the potential of creating unexpected and possibly irrelevant failures in the test suite, in particular in corner cases not covered by our buildbots. We won't see many new changes in 3.12 after this, and we won't have a lot of opportunities to fix the test failures this might uncover.

@Yhg1s Yhg1s closed this Apr 8, 2025
@graingert graingert deleted the backport-8a00c9a-3.12 branch April 8, 2025 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants