Hi, On 10/24/26 02:18, Bob Friesenhahn wrote:
This sounds like a challenging feature. Assuming that issues like the process tree being reaped can be dealt with, have you considered how to deal with the possible carnage (e.g. temporary files or even something like system networking left in a bad state) which may occur if a test is forcibly stopped? If a test is not allowed to clean up, then it may fail later due to an unexpected state when 'make test' is run again.
Maybe TESTCLEANFILES or <testname>_TESTCLEAN would be a solution."distcheck" would check that none of these exist after "make all" or "make check", and these should not overlap if parallel tests are enabled.
Maybe a standard interface for requesting that tests leave temporary files behind is also useful here, both for users directly and to verify that TESTCLEANFILES is complete.
Simon
OpenPGP_signature.asc
Description: OpenPGP digital signature
