Mir

Comment 1 for bug 1231341

Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

I don't think a collection like this is a useful bug report - as individual tests are likely to be fixed separately.

However, I can reproduce the ClientPidTestFixture failure, and see a "Broken pipe" error indicating that the server is disconnecting from the socket:

$ MIR_CLIENT_RPC_REPORT=log bin/acceptance-tests --gtest_filter=ClientPidTestFixture.* --gtest_repeat=1000 --gtest_break_on_failure
...
Repeating all tests (iteration 688) . . .

Note: Google Test filter = ClientPidTestFixture.*
[==========] Running 2 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 2 tests from ClientPidTestFixture
[ RUN ] ClientPidTestFixture.session_authorizer_receives_pid_of_connecting_clients

GMOCK WARNING:
Uninteresting mock function call - returning default value.
    Function call: configure_display_is_allowed(16787)
          Returns: false
Stack trace:
[DD, rpc] Invocation request: id: 0 method_name: connect
[DD, rpc] Invocation succeeded: id: 0 method_name: connect
[DD, rpc] Result received: id: 0
[DD, rpc] Complete response: id: 0
[DD, rpc] Invocation request: id: 1 method_name: disconnect
[DD, rpc] Invocation succeeded: id: 1 method_name: disconnect
[DD, rpc] Result received: id: 1
[DD, rpc] Complete response: id: 1
[ OK ] ClientPidTestFixture.session_authorizer_receives_pid_of_connecting_clients (14 ms)
[ RUN ] ClientPidTestFixture.authorizer_may_prevent_connection_of_clients
[DD, rpc] Invocation request: id: 0 method_name: connect
[EE, rpc] Invocation failed: id: 0 method_name: connect error: Broken pipe
pure virtual method called
terminate called without an active exception
/home/alan/display_server/development-branch/tests/mir_test_framework/testing_process_manager.cpp:127: Failure
Value of: result.succeeded()
  Actual: false
Expected: true
client terminate error=process::Result(child_terminated_by_signal, signal(6), )
Segmentation fault (core dumped)