Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail
Bug #1612012 reported by
Daniel van Vugt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Confirmed
|
Medium
|
Alexandros Frantzis | ||
0.24 |
Fix Released
|
Medium
|
Alexandros Frantzis | ||
mir (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Tests always fail together: ServerDisconnect, ServerStartup, UnresponsiveClient
17:27:52 9: [ FAILED ] 5 tests, listed below:
17:27:52 9: [ FAILED ] ServerDisconnec
17:27:52 9: [ FAILED ] ServerDisconnec
17:27:52 9: [ FAILED ] ServerStartup.
17:27:52 9: [ FAILED ] ServerStartup.
17:27:52 9: [ FAILED ] UnresponsiveCli
This is happening regularly in CI. These failures occur together.
Related branches
lp://qastaging/~afrantzis/mir/fix-1612012
- Cemil Azizoglu (community): Approve
- Mir CI Bot: Approve (continuous-integration)
- Alan Griffiths: Approve
- Kevin DuBois (community): Approve
-
Diff: 133 lines (+107/-0)3 files modifiedsrc/server/graphics/nested/display_buffer.cpp (+1/-0)
tests/unit-tests/platforms/nested/CMakeLists.txt (+1/-0)
tests/unit-tests/platforms/nested/test_nested_display_buffer.cpp (+105/-0)
Changed in mir: | |
assignee: | nobody → Alexandros Frantzis (afrantzis) |
Changed in mir: | |
milestone: | none → 0.25.0 |
Changed in mir: | |
milestone: | 0.25.0 → 0.26.0 |
Changed in mir: | |
milestone: | 0.26.0 → none |
Changed in mir: | |
importance: | High → Medium |
To post a comment you must log in.
This is happening too often. Bumping importance.