Comment 9 for bug 1407863

It's also a little bit suspicious that we're hitting the Valgrind unhandled instruction problem at exactly the same time:

[ RUN ] GLibMainLoopTest.propagates_exception_from_signal_handler
==15334==
==15334== HEAP SUMMARY:
==15334== in use at exit: 32,289 bytes in 522 blocks
==15334== total heap usage: 31,911 allocs, 31,389 frees, 1,658,903 bytes allocated
==15334==
==15334== LEAK SUMMARY:
==15334== definitely lost: 0 bytes in 0 blocks
==15334== indirectly lost: 0 bytes in 0 blocks
==15334== possibly lost: 5,836 bytes in 159 blocks
==15334== still reachable: 26,453 bytes in 363 blocks
==15334== suppressed: 0 bytes in 0 blocks
==15334== Reachable blocks (those to which a pointer was found) are not shown.
==15334== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==15334==
==15334== For counts of detected and suppressed errors, rerun with: -v
==15334== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 3 from 3)
unknown file: Failure
C++ exception with description "Timeout while waiting for child to change state" thrown in the test body.
disInstr(thumb): unhandled instruction: 0xDEFF 0xF893
[ FAILED ] GLibMainLoopTest.propagates_exception_from_signal_handler (5953 ms)

[https://jenkins.qa.ubuntu.com/job/mir-ubuntu-vivid-armhf-ci/21/consoleFull]

Unhandled instructions will of course (should) lead to test failures.