Repository navigation
gh-75876: Report the peak memory use of a bigmem test - #156024
Merged
serhiy-storchaka merged 1 commit intoAug 19, 2026
Merged
serhiy-storchaka merged 1 commit into
serhiy-storchaka merged 1 commit into
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
In verbose mode, report how much memory the test really used, next to how much it declared. The subprocess measures its own peak; if it died before reporting it, the parent reports what it sampled, as a lower bound. Report also the number of major page faults, if any: the test did not fit in memory, so its timing means little. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
serhiy-storchaka
added a commit
to serhiy-storchaka/cpython
that referenced
this pull request
Aug 20, 2026
The memory watchdog now both reports the peak (pythonGH-156024) and kills a test which uses more memory than it declares.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In verbose mode, report how much memory the test really used, next to how much it declared:
The subprocess measures its own peak; if it died before reporting it, the parent reports what it sampled, as a lower bound.
Report also the number of major page faults, if any: the test did not fit in memory, so its timing means little.