Test failed but really just looks like an assertion failure inside pthreads:
04:22:35 [ RUN ] ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error
04:22:35
04:22:35 [WARNING] /usr/src/gtest/src/gtest-death-test.cc:825:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads.
04:22:35 /<<BUILDDIR>>/mir-0.25.0+xenial3092bzr3867/tests/unit-tests/dispatch/test_threaded_dispatcher.cpp:416: Failure
04:22:35 Death test: { ::mir::test::disable_core_dump(); { { md::ThreadedDispatcher* dispatcher; auto dispatchable = std::make_shared<mt::TestDispatchable>([&dispatcher]() { delete dispatcher; }); dispatchable->trigger(); dispatcher = new md::ThreadedDispatcher("Death thread", dispatchable); std::this_thread::sleep_for(10s); } ; } }
04:22:35 Result: died but not with expected error.
04:22:35 Expected: .*Destroying ThreadedDispatcher.*
04:22:35 Actual msg:
04:22:35 [ DEATH ] mir_unit_tests.bin: tpp.c:84: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio >= fifo_min_prio && new_prio <= fifo_max_prio)' failed.
04:22:35 [ DEATH ]
04:22:35 [ FAILED ] ThreadedDispatcherDeathTest.destroying_dispatcher_from_a_callback_is_an_error (159 ms)
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3063/consoleFull
I wonder whether this isn't fallout of us using a known-buggy-