Indeed the cause is again valgrind errors in NestedServer tests. But should we be reusing the same bug? Just search for "==12777==":
20:13:30 9: [----------] 25 tests from NestedServer 20:13:30 9: [ RUN ] NestedServer.nested_platform_connects_and_disconnects 20:13:31 9: [2016-11-02 20:13:31.685261] mirserver: Starting 20:13:31 9: [2016-11-02 20:13:31.689667] mirserver: Selected driver: mir:stub-graphics (version 0.25.0) 20:13:31 9: [2016-11-02 20:13:31.733003] mirserver: Using software cursor 20:13:32 9: [2016-11-02 20:13:32.118804] mirserver: Selected input driver: mir:stub-input (version: 0.25.0) 20:13:32 9: [2016-11-02 20:13:32.128108] mirserver: Mir version 0.25.0 20:13:32 9: [2016-11-02 20:13:32.211391] mirserver: Starting 20:13:34 9: [2016-11-02 20:13:34.070068] mirserver: Using nested cursor 20:13:34 9: ==12777== Thread 9: 20:13:34 9: ==12777== Invalid read of size 4 20:13:34 9: ==12777== at 0x540688F: MirWaitHandle::wait_for_all()::$_0::operator()() const (mir_wait_handle.cpp:53) 20:13:34 9: ==12777== by 0x5406401: void std::condition_variable::wait<MirWaitHandle::wait_for_all()::$_0>(std::unique_lock<std::mutex>&, MirWaitHandle::wait_for_all()::$_0) (condition_variable:98) 20:13:34 9: ==12777== by 0x5406376: MirWaitHandle::wait_for_all() (mir_wait_handle.cpp:53) 20:13:34 9: ==12777== by 0x54774D9: mir_connection_create_buffer_stream_sync (mir_buffer_stream_api.cpp:76) 20:13:34 9: ==12777== by 0x517576D: (anonymous namespace)::MirClientHostSurface::set_cursor_image(mir::graphics::CursorImage const&) (mir_client_host_connection.cpp:168) 20:13:34 9: ==12777== by 0x5175D95: mir::graphics::nested::MirClientHostConnection::set_cursor_image(mir::graphics::CursorImage const&) (mir_client_host_connection.cpp:430) .... -- 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: Confirmed 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 : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
