Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
gh-118846: Fix free-threading test failures when run sequentially#118864
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
The free-threaded build currently immortalizes some objects once thefirst thread is started. This can lead to test failures depending on theorder in which tests are run. This PR addresses those failures bysuppressing immortalization or skipping the affected tests.
colesbury commentedMay 9, 2024
DinoV left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM!
hroncok commentedMay 9, 2024 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I still have: Not sure if the pydoc thing is related, but the gc might. |
colesbury commentedMay 9, 2024
The pydoc failure is a funny interaction between tests. In cpython/Lib/test/test_inspect/test_inspect.py Lines 771 to 775 in98ff3f6
In the free-threaded build, this class is now immortalized so it's still alive later on when |
colesbury commentedMay 10, 2024
Ok, I think the |
Thanks@colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…ly (pythonGH-118864)The free-threaded build currently immortalizes some objects once thefirst thread is started. This can lead to test failures depending on theorder in which tests are run. This PR addresses those failures bysuppressing immortalization or skipping the affected tests.(cherry picked from commitb309c8e)Co-authored-by: Sam Gross <colesbury@gmail.com>
GH-118927 is a backport of this pull request to the3.13 branch. |
…lly (GH-118864) (#118927)The free-threaded build currently immortalizes some objects once thefirst thread is started. This can lead to test failures depending on theorder in which tests are run. This PR addresses those failures bysuppressing immortalization or skipping the affected tests.(cherry picked from commitb309c8e)Co-authored-by: Sam Gross <colesbury@gmail.com>
hroncok commentedMay 10, 2024
This is the only one I got now: |
colesbury commentedMay 10, 2024
Just checking, this is from |
AlexWaygood commentedMay 10, 2024
Note that that AST test was only merged (and backported to 3.13) yesterday in#118854 |
hroncok commentedMay 11, 2024
I might have git pulled but forgot to rebuild it. Mea culpa. Trying fresh. |
hroncok commentedMay 11, 2024
All is good now, thank you! |
…ly (python#118864)The free-threaded build currently immortalizes some objects once thefirst thread is started. This can lead to test failures depending on theorder in which tests are run. This PR addresses those failures bysuppressing immortalization or skipping the affected tests.
Uh oh!
There was an error while loading.Please reload this page.
The free-threaded build currently immortalizes some objects once the first thread is started. This can lead to test failures depending on the order in which tests are run. This PR addresses those failures by suppressing immortalization or skipping the affected tests.