Skip to content

[3.14] gh-75876: Run bigmem tests in a subprocess (GH-155302) - #156013

Merged
serhiy-storchaka merged 1 commit into
python:3.14from
serhiy-storchaka:bigmem-subprocess-314
Oct 9, 2026
Merged

serhiy-storchaka merged 1 commit into
python:3.14from
serhiy-storchaka:bigmem-subprocess-314

Conversation

@serhiy-storchaka

@serhiy-storchaka serhiy-storchaka commented Aug 18, 2026 •

Copy link
Copy Markdown
Member

Manual backport: the cherry-pick conflicted, and get_process_memory_usage() (gh-150114) is not available on this branch.

The parent process therefore does not report the memory usage of the subprocess. Everything else is as in the main branch.

)

A test which really allocates the memory it asks for (that is, run with -M)
now runs in a subprocess, so that the memory it uses and the address space
it fragments are released when it ends.  A dummy run stays in the process.

The separate watchdog process is no longer used.  Unlike in the main branch,
the parent process does not report the memory usage of the subprocess:
get_process_memory_usage() (pythongh-150114) is not available on this branch.

(cherry picked from commit 66d7c89)

Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
@serhiy-storchaka serhiy-storchaka added the tests Tests in the Lib/test dir label Aug 18, 2026
@serhiy-storchaka
serhiy-storchaka merged commit 2a76adb into python:3.14 Oct 9, 2026
53 checks passed
@serhiy-storchaka
serhiy-storchaka deleted the bigmem-subprocess-314 branch October 9, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tests Tests in the Lib/test dir

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant