gstreamer/libs/gst
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
..
base baseparse: remove duplicate code 2015-03-17 19:35:08 +00:00
check check: Catch SIGTERM and SIGINT in the test runner and kill all currently running tests 2015-03-21 15:19:43 +01:00
controller timedvaluecontrolsource: Do not wrongly send value-removed 2015-02-13 19:59:57 +01:00
helpers helpers: Fix install of completion-helper. 2015-02-24 14:11:45 +01:00
net meta: Add GstNetControlMessageMeta 2015-03-14 13:54:51 +01:00
Makefile.am dist net directory only once 2012-03-21 12:10:21 +01:00