avocado.job: On interrupt, don't explicitly raise exceptions

So we don't trigger multiprocess logging inadvertedly.
Just fill out the instance with appropriate data.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
avocado.job: Try to get test state once more before filling abort state

This way we can correctly catch tests that just timed out.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
selftests/functional: Ensure no abort error message appears on time out

This way we avoid the bug that was fixed on the previous commit.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
avocado.job: Send SIGKILL on Ctrl+C to all subprocesses

Turns out some subprocesses might misbehave (see tests
like trinity - run on a VM), so it's not enough to send
the interrupt signal. For a clean stop output wise,
SIGKILL is necessary.

As a side effect, the previous Ctrl+C can be resurrected,
this time renamed to _interrupt, since we're not really
simulating Ctrl+C.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Merge pull request #140 from lmr/interrupt-fixes

Interrupt fixes