Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 34k
GH-91079: Implement C stack limits using addresses, not counters.#130007
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
Uh oh!
There was an error while loading. Please reload this page.
Conversation
markshannon commented Feb 11, 2025 • edited by bedevere-app bot
Loading Uh oh!
There was an error while loading. Please reload this page.
edited by bedevere-app bot
Uh oh!
There was an error while loading. Please reload this page.
…m independent constants
Thanks for making the requested changes! @iritkatriel, @encukou: please review the changes made to this pull request. |
encukou 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.
Looks great now, thank you!
Would you be OK with me asking the SC to remove Py_C_RECURSION_LIMIT (and c_recursion_remaining) without deprecation? IMO it's the right thing to do here.
markshannon commented Feb 19, 2025
Sure, go ahead. I was thinking that we should deprecate the whole of |
2498c22 into python:mainUh oh!
There was an error while loading. Please reload this page.
bedevere-bot commented Feb 19, 2025
|
bedevere-bot commented Feb 19, 2025
|
brettcannon commented Feb 19, 2025
@markshannon if you look at line 427 of https://buildbot.python.org/#/builders/1046/builds/7562/steps/8/logs/stdio you will see that |
brettcannon commented Feb 19, 2025
I opened #130319 and assigned it to @markshannon . |
freakboy3742 commented Feb 20, 2025
This also appears to have caused a failure on the iOS buildbot (masked because there was an existing failure with the colorise tests). However, this build, triggered by the merge of this PR is the first one that has a failure in test_sys |
freakboy3742 commented Feb 20, 2025
@markshannon Looking into the iOS failure - the comment before the test that is failing says: What constitutes "normal" here? Is it possible a sequential, single process run (i.e., how iOS runs the test suite) might trigger this? I'm a bit out my depth here on diagnosing the cause of this one, so any pointers or suggestions for possible causes would be most welcome. |
markshannon commented Feb 20, 2025
This PR does no refcounting, allocation or deallocation. |
freakboy3742 commented Feb 20, 2025
@markshannon I've opened #130384 to track the problem. Annoyingly, I can't reproduce this locally - the test passes reliably on my own iOS test setup. |
… counters. (pythonGH-130007)" for now Unfortunatlely, the change broke some buildbots. This reverts commit 2498c22.
…its using addresses, not counters. (pythonGH-130007)" for now (GH130413)" This reverts commit ef29104.
Hopefully, this will also fix#113655.