| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| @@ -0,0 +1,2 @@ | |||
| Restore the recursion limit after the free-threading recursion-limit race test | |||
There was a problem hiding this comment.
Test only changes don't requires a news entry file, please remove it.
Sorry, something went wrong.
There was a problem hiding this comment.
'Tests' is one of the blurb options, for test-only PRs, and this was put in the Tests section.
Sorry, something went wrong.
There was a problem hiding this comment.
The DevGuide has some wording on this: https://github.com/python/devguide/blob/b89ba85ad4d34984812210f6460d619565839971/getting-started/pull-request-lifecycle.rst?plain=1#L218-L219. So does this mean a NEWS entry is just optional for test-only changes?
However, I've seen other test-only PRs where the author was asked to remove the NEWS entry:
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the fix!
Sorry, something went wrong.
|
Thanks @zolaski333 for the PR, and @freakboy3742 for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
Sorry, something went wrong.
|
GH-159389 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-159390 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
test_racing_recursion_limit leaves the interpreter's recursion limit at 199. When tests share a process, the Python lru_cache recursion test and 68 pickle cases subsequently raise RecursionError.
Register a cleanup to restore the original recursion limit even if the race test fails. This preserves the existing concurrency test and follows the TestCase.addCleanup pattern used elsewhere in the suite.
Fixes gh-159293.
Validation on Windows x64, CPython main at 50082b8d893, free-threaded Release build with the GIL disabled: