Skip to content
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

gh-128770: raise warnings as errors in test suite - except for test_socket which still logs warnings, and internal test warnings that are now logged #128973

Merged
merged 54 commits into from
Mar 27, 2025

Conversation

graingert
Copy link
Contributor

@graingert graingert commented Jan 18, 2025

@graingert
Copy link
Contributor Author

@hugovk can I get a run on the buildbots for this PR?

@hugovk
Copy link
Member

hugovk commented Jan 18, 2025

Certainly!

Let's check if you can do it yourself: either apply one of the test-with-buildbots or test-with-refleak-buildbots labels, or add a comment like ! buildbot optional-regex (but no space between exclamation mark and buildbot) to run a subset.

@graingert graingert added the 🔨 test-with-buildbots Test PR w/ buildbots; report in status section label Jan 18, 2025
@bedevere-bot
Copy link

🤖 New build scheduled with the buildbot fleet by @graingert for commit c06c3db 🤖

If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again.

@bedevere-bot bedevere-bot removed the 🔨 test-with-buildbots Test PR w/ buildbots; report in status section label Jan 18, 2025
@graingert graingert added the 🔨 test-with-buildbots Test PR w/ buildbots; report in status section label Jan 18, 2025
@bedevere-bot
Copy link

🤖 New build scheduled with the buildbot fleet by @graingert for commit 7123093 🤖

If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again.

@bedevere-bot bedevere-bot removed the 🔨 test-with-buildbots Test PR w/ buildbots; report in status section label Jan 18, 2025
@graingert
Copy link
Contributor Author

@hugovk do you know where I can see the status?

@hugovk
Copy link
Member

hugovk commented Jan 18, 2025

You can click the "Details" links in the status checks:

image image

Some of those failing ones were already failing for previous builds, so aren't necessarily caused by this PR.

@graingert
Copy link
Contributor Author

You can click the "Details" links in the status checks:
image image

Some of those failing ones were already failing for previous builds, so aren't necessarily caused by this PR.

Ah those hadn't shown up yet

@graingert graingert marked this pull request as ready for review January 18, 2025 22:48
@hugovk
Copy link
Member

hugovk commented Mar 27, 2025

The warnings have been fixed in other PRs in main, and this PR is back to turning future warnings into errors. If there are no objections, I'll merge this later today.

@hugovk hugovk merged commit 8a00c9a into python:main Mar 27, 2025
46 checks passed
@miss-islington-app
Copy link

Thanks @graingert for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

@miss-islington-app
Copy link

Sorry, @graingert and @hugovk, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 8a00c9a4d2ce9d373b13f8f0a2265a65f4523293 3.13

@miss-islington-app
Copy link

Sorry, @graingert and @hugovk, I could not cleanly backport this to 3.12 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker 8a00c9a4d2ce9d373b13f8f0a2265a65f4523293 3.12

@bedevere-app
Copy link

bedevere-app bot commented Mar 27, 2025

GH-131802 is a backport of this pull request to the 3.13 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.13 bugs and security fixes label Mar 27, 2025
graingert added a commit to graingert/cpython that referenced this pull request Mar 27, 2025
…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)
@bedevere-bot
Copy link

⚠️⚠️⚠️ Buildbot failure ⚠️⚠️⚠️

Hi! The buildbot aarch64 Fedora Stable LTO 3.x (tier-2) has failed when building commit 8a00c9a.

What do you need to do:

  1. Don't panic.
  2. Check the buildbot page in the devguide if you don't know what the buildbots are or how they work.
  3. Go to the page of the buildbot that failed (https://buildbot.python.org/#/builders/336/builds/6580) and take a look at the build logs.
  4. Check if the failure is related to this commit (8a00c9a) or if it is a false positive.
  5. If the failure is related to this commit, please, reflect that on the issue and make a new Pull Request with a fix.

You can take a look at the buildbot page here:

https://buildbot.python.org/#/builders/336/builds/6580

Summary of the results of the build (if available):

==

Click to see traceback logs
Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 1054, in _bootstrap_inner
    self.run()
    ~~~~~~~~^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 996, in run
    self._target(*self._args, **self._kwargs)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py", line 30, in task
    interp = interpreters.create()
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py", line 76, in create
    id = _interpreters.create(reqrefs=True)
interpreters.InterpreterError: interpreter creation failed
k


Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 1054, in _bootstrap_inner
    self.run()
    ~~~~~~~~^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 996, in run
    self._target(*self._args, **self._kwargs)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py", line 47, in run
    interp = interpreters.create()
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py", line 76, in create
    id = _interpreters.create(reqrefs=True)
interpreters.InterpreterError: interpreter creation failed
k

@graingert
Copy link
Contributor Author

the failure is related to this commit, however the code in this PR is working as intended. This has uncovered an issue in subinterpreters:

test_create_many_threaded (test.test_interpreters.test_stress.StressTests.test_create_many_threaded) ... Warning -- Uncaught thread exception: InterpreterError
Exception in thread Thread-166 (task):
RuntimeError: Failed to import encodings module
During handling of the above exception, another exception occurred:
interpreters.InterpreterError: sub-interpreter creation failed
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 1054, in _bootstrap_inner
    self.run()
    ~~~~~~~~^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/threading.py", line 996, in run
    self._target(*self._args, **self._kwargs)
    ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/test_interpreters/test_stress.py", line 30, in task
    interp = interpreters.create()
  File "/home/buildbot/buildarea/3.x.cstratak-fedora-stable-aarch64.lto/build/Lib/test/support/interpreters/__init__.py", line 76, in create
    id = _interpreters.create(reqrefs=True)
interpreters.InterpreterError: interpreter creation failed

@ZeroIntensity
Copy link
Member

That's a known failure, don't worry about it.

@graingert
Copy link
Contributor Author

Ah you're right it's not a Warning that got raised as an Exception! I panicked like the message said not to

@bedevere-app
Copy link

bedevere-app bot commented Mar 28, 2025

GH-131824 is a backport of this pull request to the 3.12 branch.

@bedevere-app bedevere-app bot removed the needs backport to 3.12 bug and security fixes label Mar 28, 2025
diegorusso pushed a commit to diegorusso/cpython that referenced this pull request Apr 1, 2025
…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]>
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.

8 participants