Sebastian Dröge 7646cef644 check: Catch SIGTERM and SIGINT in the test runner and kill all currently running tests ... Otherwise e.g. ctrl+c in the test runner exits the test runner, while the test itself is still running in the background, uses CPU and memory and potentially never exits (e.g. if the test ran into a deadlock or infinite loop). The reason why we have to manually kill the actual tests is that after forking they will be moved to their own process group, and as such are not receiving any signals sent to the test runner anymore. This is supposed to be done to make it easier to kill a test, which it only really does if the test itself is forking off new processes. This fix is not complete though. SIGKILL can't be caught at all, and error signals like SIGSEGV, SIGFPE are currently not caught. The latter will only happen if there is a bug in the test runner itself, and as such seem less important.		2015-03-21 15:19:43 +01:00
..
gst	check: Catch SIGTERM and SIGINT in the test runner and kill all currently running tests	2015-03-21 15:19:43 +01:00
Makefile.am	android: make it ready for androgenizer	2011-04-11 01:08:07 +02:00