Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
[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 ourterms of service andprivacy 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
…test_socket which still logs warnings, and internal test warnings that are now logged (python#128973)Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>(cherry picked from commit8a00c9a)
Uh oh!
There was an error while loading.Please reload this page.
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. |
Uh oh!
There was an error while loading.Please reload this page.
…ocket which still logs warnings, and internal test warnings that are now logged (#128973)
Co-authored-by: Bénédikt Tran10796600+picnixz@users.noreply.github.com
(cherry picked from commit8a00c9a)