Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork34k
gh-141794: Reduce size of compiler stress tests to fix Android warnings#142263
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
mhsmith commentedDec 7, 2025
I've updated this to change the sizes only on Android, and the tests are now passing on all platforms, so this PR is ready to review. Due to#142289, the tests are now running on API level 35, so the low memory warnings are much less detailed. Search for the |
f193c8f intopython:mainUh oh!
There was an error while loading.Please reload this page.
…warnings (pythonGH-142263)(cherry picked from commitf193c8f)Co-authored-by: Malcolm Smith <smith@chaquo.com>
Sorry,@mhsmith and@Eclips4, I could not cleanly backport this to |
GH-142386 is a backport of this pull request to the3.14 branch. |
…ndroid warnings (pythonGH-142263)(cherry picked from commitf193c8f)Co-authored-by: Malcolm Smith <smith@chaquo.com>
GH-142409 is a backport of this pull request to the3.13 branch. |
Uh oh!
There was an error while loading.Please reload this page.
This fixes the Android low memory warnings in
test_astandtest_compile, previously discussed in#137186 (comment).These warnings haven't led to a crash so far. However, the warning will only appear during the first test that brings the memory below a threshold. If a later test exhausts the memory completely, then the warning won't appear again, and the process will simply crash. This separation between the warning and the crash makes the crash much more difficult to understand.
I think this may have been what happened in#142228 (comment), which introduced some leaks. Notice inthis run, the warning appeared during
test_ast, and the crash happened intest_random.