-
-
Notifications
You must be signed in to change notification settings - Fork 32k
Some tests consume too much memory #133454
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
Comments
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
May 5, 2025
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
May 5, 2025
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
May 5, 2025
…nd_releasebuf The original reproducer only used 10 threads.
serhiy-storchaka
added a commit
that referenced
this issue
May 8, 2025
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 8, 2025
… bigmem (pythonGH-133456) (cherry picked from commit 26839ea) Co-authored-by: Serhiy Storchaka <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 8, 2025
… bigmem (pythonGH-133456) (cherry picked from commit 26839ea) Co-authored-by: Serhiy Storchaka <[email protected]>
serhiy-storchaka
added a commit
that referenced
this issue
May 8, 2025
…s bigmem (GH-133456) (GH-133664) (cherry picked from commit 26839ea) Co-authored-by: Serhiy Storchaka <[email protected]>
serhiy-storchaka
added a commit
that referenced
this issue
May 8, 2025
…s bigmem (GH-133456) (GH-133663) (cherry picked from commit 26839ea) Co-authored-by: Serhiy Storchaka <[email protected]>
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this issue
May 23, 2025
50 producer and 50 consumer threads need more than 5GB of memory.
serhiy-storchaka
added a commit
that referenced
this issue
May 23, 2025
…easebuf (GH-133458) The original reproducer only used 10 threads.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 23, 2025
…nd_releasebuf (pythonGH-133458) The original reproducer only used 10 threads. (cherry picked from commit fc0c9c2) Co-authored-by: Serhiy Storchaka <[email protected]>
serhiy-storchaka
added a commit
that referenced
this issue
May 23, 2025
…and_releasebuf (GH-133458) (GH-134589) The original reproducer only used 10 threads. (cherry picked from commit fc0c9c2) Co-authored-by: Serhiy Storchaka <[email protected]>
I think it's all for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Several years ago, all tests, except bigmem tests could be ran sequentially with just 650 MB of memory. There were issues with some buldbots (e.g. AIX) which small RAM, because excess memory consumption not always caused a quick test failure, but could cause swapping and failing tests at timeout 2 hours later. So all tests with high memory consumption were decorated with
bigmemtest
.Now, some tests need more than 1 GB of memory, or even more than 2 GB. Not all buildbots have such much.
The main culprit is running too many threads. Every thread needs 35, 70 or even 90 MB, depending on test.
There are two possible solutions:
bigmemtest
. This will skip it on most buildbots.Linked PRs
The text was updated successfully, but these errors were encountered: