ClientLibraryErrorsDeathTest is dumping core, causing spurious problem reports (like this one)

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding mir. This problem was most recently seen with version 0.9.0+15.04.20141125-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/318a0132ff5aca50838dfffb9bdbe88d1edebf01 contains more details.

[Daniel van Vugt (vanvugt)]

Hmm, not a bug:

#2 0xb6a68b4e in __GI_abort () at abort.c:89
#3 0xb6da62de in mir_connection_create_surface (connection=0x1, params=0xbeb95834,
#4 0xb6da6424 in mir_connection_create_surface_sync (connection=<optimized out>,
#5 0x0019ebe2 in ClientLibraryErrorsDeathTest_createing_surface_on_garbage_connection_is_fatal_Test::TestBody (this=<optimized out>) at /build/buildd/mir-0.9.0+15.04.20141125/tests/acceptance-tests/test_client_library_errors.cpp:298
        gtest_sentinel = {test_ = 0x226fd80}

I'm sure this has been an issue before (duplicate?). We just have to stop it emitting SIGABRT and generating problem reports.

[Daniel van Vugt (vanvugt)]

Also related: bug 1342092

[Alan Griffiths (alan-griffiths)]

The abort in this (and related) tests is correct: it is the behaviour being tested for.

The error is in such tests being reported by Ubuntu Error Tracker - is there any way to flag executables as "do not error track"?

[Daniel van Vugt (vanvugt)]

Yes, just catch SIGABRT in the test and/or drop it completely [signal(SIGABRT, SIG_IGN)]

[Daniel van Vugt (vanvugt)]

We need a general solution for this. I'll put it in with bug 1342092