test_repr_lock leaves a dangling process

[serhiy-storchaka]

Bug report

test_repr_lock starts the process P2, terminates it and never joins it, so it is still in multiprocessing.active_children() when the test ends:

$ ./python -m test --fail-env-changed test.test_multiprocessing_fork.test_processes -m test.test_multiprocessing_fork.test_processes.WithProcessesTestLock.test_repr_lock
Warning -- Dangling processes: {<Process name='P2' pid=3761884 parent=3761868 stopped exitcode=-SIGTERM>}
Result: ENV CHANGED

The same for the forkserver and spawn variants.

Running the whole file passes: the process is reaped before the environment is checked.

Linked PRs

• gh-155732: Join the terminated process in test_repr_lock #155734
• [3.15] gh-155732: Join the terminated process in test_repr_lock (GH-155734) #155766
• [3.14] gh-155732: Join the terminated process in test_repr_lock (GH-155734) #155767
• [3.13] gh-155732: Join the terminated process in test_repr_lock (GH-155734) #155768