Merge lp://qastaging/~afrantzis/mir/fix-1517781-double-close into lp://qastaging/mir
Proposed by
Alexandros Frantzis
Status: | Merged |
---|---|
Approved by: | Alberto Aguirre |
Approved revision: | no longer in the source branch. |
Merged at revision: | 3111 |
Proposed branch: | lp://qastaging/~afrantzis/mir/fix-1517781-double-close |
Merge into: | lp://qastaging/mir |
Diff against target: |
49 lines (+6/-7) 2 files modified
include/test/mir_test_framework/async_server_runner.h (+1/-3) tests/mir_test_framework/async_server_runner.cpp (+5/-4) |
To merge this branch: | bzr merge lp://qastaging/~afrantzis/mir/fix-1517781-double-close |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
PS Jenkins bot (community) | continuous-integration | Approve | |
Alberto Aguirre (community) | Approve | ||
Alan Griffiths | Approve | ||
Review via email: mp+278032@code.qastaging.launchpad.net |
Commit message
tests: Avoid double-closing the mir connection fd
Description of the change
tests: Avoid double-closing the mir connection fd
Besides being obviously wrong, it can lead to very mysterious failures in completely unrelated parts of the code (see bug 1517781).
I wonder if this is the cause of any other mysterious failures we have seen.
To post a comment you must log in.
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?