Issue 37711: regrtest: re-run failed tests in subprocesses

➜

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/81892

classification

Title:	regrtest: re-run failed tests in subprocesses
Type:		Stage:
Components:	Tests	Versions:	Python 3.9

process

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

Created on 2019-07-29 23:44 by vstinner, last changed 2022-04-11 14:59 by admin.

Messages (1)
msg348700 - (view)	Author: STINNER Victor (vstinner) *	Date: 2019-07-29 23:44
When using python3 -m test -w, failed tests are re-run in the regrtest main process, even if -jN option is used. If a test does crash, regrtest doesn't remove its temporary directory which can lead to random test failures like bpo-37359. At least when using -jN, I suggest to run tests in a subprocess to ensure that regrtest is able to cleanup its temporary directory, even if a test does crash.

msg348700 - (view)

Author: STINNER Victor (vstinner) * (Python committer)

Date: 2019-07-29 23:44

When using python3 -m test -w, failed tests are re-run in the regrtest main process, even if -jN option is used. If a test does crash, regrtest doesn't remove its temporary directory which can lead to random test failures like bpo-37359.

At least when using -jN, I suggest to run tests in a subprocess to ensure that regrtest is able to cleanup its temporary directory, even if a test does crash.

History
Date	User	Action	Args
2022-04-11 14:59:18	admin	set	github: 81892
2019-07-29 23:45:04	vstinner	set	title: regrtest: re-run tests in subprocesses -> regrtest: re-run failed tests in subprocesses
2019-07-29 23:44:36	vstinner	create