This bug was fixed in the package mir - 0.24.1+16.10.20160928-0ubuntu1 --------------- mir (0.24.1+16.10.20160928-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.1 (https://launchpad.net/mir/+milestone/0.24.1) - ABI summary: . All ABI numbers remain unchanged. . mircommon ABI at 6, but now including a symbol misplaced in 0.24.0 - Bugs fixed: . mirserver ignored further keymap configuration changes after a keyboard is configured (LP: #1626435) . fix for libmircommon.so.6 ABI break: version stanza of mir::dispatch::ReadableFd* moved to newer version (LP: #1617865) . clang builds fail (again) (LP: #1609612) . Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail (LP: #1612012) . Break potentially infinite loop in search for next session to focus (LP: #1625401) -- Andreas Pokorny <andreas.poko...@canonical.com> Wed, 28 Sep 2016 12:09:49 +0000 ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1612012 Title: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail Status in Mir: Fix Committed Status in Mir 0.24 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Tests always fail together: ServerDisconnect, ServerStartup, UnresponsiveClient 17:27:52 9: [ FAILED ] 5 tests, listed below: 17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client 17:27:52 9: [ FAILED ] ServerDisconnect.doesnt_stop_client_calling_API_functions 17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem 17:27:52 9: [ FAILED ] ServerStartup.after_server_sigkilled_can_start_new_instance 17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server [https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull] This is happening regularly in CI. These failures occur together. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1612012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
