Still happening in the 0.24 branch:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/2340/consoleFull
** Also affects: mir/0.24
Importance: Undecided
Status: New
** Changed in: mir/0.24
Milestone: None => 0.24.1
** Changed in: mir/0.24
Importance: Undecided => Medium
** Changed in: mir/0.24
Status: New => Triaged
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Importance: Undecided => Medium
** Changed in: mir (Ubuntu)
Status: New => Triaged
** Changed in: mir/0.24
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
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:
Triaged
Status in mir package in Ubuntu:
Triaged
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
