Issue 46999: test_multiprocessing_fork running without any timeout

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/91155

classification

Title:	test_multiprocessing_fork running without any timeout
Type:		Stage:
Components:	Tests	Versions:

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	doko
Priority:	normal	Keywords:

Created on 2022-03-13 05:17 by doko, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg415027 - (view)	Author: Matthias Klose (doko) *	Date: 2022-03-13 05:17
the test_multiprocessing_fork test is a bit unreliable, at least on both the Debian and Ubuntu test infrastructures, sometimes running for 100+ hours. When running locally, I cannot reproduce these issues. Note that the test and build infrastructure is usually limited to 4-6 cores and 20GB of RAM (including swap). What else could be an issue for these hangs? How can this test reliably timeout? I know it takes a few hours on slow architectures even when succeeding.

msg415027 - (view)

Author: Matthias Klose (doko) * (Python committer)

Date: 2022-03-13 05:17

the test_multiprocessing_fork test is a bit unreliable, at least on both the Debian and Ubuntu test infrastructures, sometimes running for 100+ hours.  When running locally, I cannot reproduce these issues.  Note that the test and build infrastructure is usually limited to 4-6 cores and 20GB of RAM (including swap). What else could be an issue for these hangs?

How can this test reliably timeout?  I know it takes a few hours on slow architectures even when succeeding.

History
Date	User	Action	Args
2022-04-11 14:59:57	admin	set	github: 91155
2022-03-13 05:17:57	doko	create