But I can still reproduce problems in e.g. NestedServer.display_configuration_reset_when_application_exits
Vis:
Repeating all tests (iteration 429) . . .
Note: Google Test filter = NestedServer.display_configuration_reset_when_application_exits
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from NestedServer
[ RUN ] NestedServer.display_configuration_reset_when_application_exits
/home/alan/display_server/mir3/tests/acceptance-tests/test_nested_mir.cpp:755: Failure
Value of: condition.woken()
Actual: false
Expected: true
Segmentation fault (core dumped)
So which NestedServer test failures are covered by the linked bug?
Makes sense.
But I can still reproduce problems in e.g. NestedServer. display_ configuration_ reset_when_ application_ exits
Vis:
Repeating all tests (iteration 429) . . .
Note: Google Test filter = NestedServer. display_ configuration_ reset_when_ application_ exits display_ configuration_ reset_when_ application_ exits display_ server/ mir3/tests/ acceptance- tests/test_ nested_ mir.cpp: 755: Failure
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from NestedServer
[ RUN ] NestedServer.
/home/alan/
Value of: condition.woken()
Actual: false
Expected: true
Segmentation fault (core dumped)
So which NestedServer test failures are covered by the linked bug?