You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PIT should kill the slave process executing the test(s) against the mutation(s) after some time. If the test is badly designed or the mutation fails to stop a non-deamon thread, PIT hangs forever.
I've got a project that creates a ThreadPoolExecutor and fails to shutdown() that executor after the test finishes. The threads of the executor stay alive and prevent the slaves JVM from terminating. This causes PIT to hang forever waiting for the slave process to die.
It would be better if PIT does not wait forever put applies a timeout and kills the process after the timeout.
I've attached a patch with a system test demonstrating the scenario/issue.
From stefan.p...@googlemail.com on February 09, 2012 09:31:35
PIT should kill the slave process executing the test(s) against the mutation(s) after some time. If the test is badly designed or the mutation fails to stop a non-deamon thread, PIT hangs forever.
I've got a project that creates a ThreadPoolExecutor and fails to shutdown() that executor after the test finishes. The threads of the executor stay alive and prevent the slaves JVM from terminating. This causes PIT to hang forever waiting for the slave process to die.
It would be better if PIT does not wait forever put applies a timeout and kills the process after the timeout.
I've attached a patch with a system test demonstrating the scenario/issue.
Attachment: threadpool-fails-to-shutdown.patch
Original issue: http://code.google.com/p/pitestrunner/issues/detail?id=27
The text was updated successfully, but these errors were encountered: