valgrind integration-tests: [ FAILED ] BespokeDisplayServerTestFixture.*
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Undecided
|
Alexandros Frantzis | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
valgrind bin/integration
...
[ FAILED ] 3 tests, listed below:
[ FAILED ] BespokeDisplayS
[ FAILED ] BespokeDisplayS
[ FAILED ] BespokeDisplayS
Summarized details:
[ RUN ] BespokeDisplayS
unknown file: Failure
C++ exception with description "Poll on readfd for pipe timed out" thrown in the test body.
terminate called after throwing an instance of 'boost:
what(): Poll on readfd for pipe timed out
[ FAILED ] BespokeDisplayS
[ RUN ] BespokeDisplayS
.../home/
Value of: result.succeeded()
Actual: false
Expected: true
process:
[ FAILED ] BespokeDisplayS
[ RUN ] BespokeDisplayS
==6057== Invalid read of size 8
==6057== at 0x675DCE1: mir::protobuf:
==6057== by 0x5AFB517: MirConnection:
==6057== by 0x5AF7DBC: mir_connection_
==6057== by 0x74C945: BespokeDisplayS
==6057== by 0x76A944: mir_test_
==6057== by 0x768300: mir_test_
==6057== by 0x74CAB9: BespokeDisplayS
==6057== by 0x7AA53F: void testing:
==6057== by 0x7A5927: void testing:
==6057== by 0x78D8BE: testing:
==6057== by 0x78E07D: testing:
==6057== by 0x78E6FE: testing:
==6057== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==6057==
==6057==
==6057== Process terminating with default action of signal 11 (SIGSEGV)
==6057== Access not within mapped region at address 0x0
==6057== at 0x675DCE1: mir::protobuf:
==6057== by 0x5AFB517: MirConnection:
==6057== by 0x5AF7DBC: mir_connection_
==6057== by 0x74C945: BespokeDisplayS
==6057== by 0x76A944: mir_test_
==6057== by 0x768300: mir_test_
==6057== by 0x74CAB9: BespokeDisplayS
==6057== by 0x7AA53F: void testing:
==6057== by 0x7A5927: void testing:
==6057== by 0x78D8BE: testing:
==6057== by 0x78E07D: testing:
==6057== by 0x78E6FE: testing:
==6057== If you believe this happened as a result of a stack
==6057== overflow in your program's main thread (unlikely but
==6057== possible), you can try to increase the size of the
==6057== main thread stack using the --main-stacksize= flag.
==6057== The main thread stack size used in this run was 8388608.
==6057==
==6057== HEAP SUMMARY:
==6057== in use at exit: 56,749 bytes in 829 blocks
==6057== total heap usage: 3,081 allocs, 2,252 frees, 229,994 bytes allocated
==6057==
==6057== LEAK SUMMARY:
==6057== definitely lost: 0 bytes in 0 blocks
==6057== indirectly lost: 0 bytes in 0 blocks
==6057== possibly lost: 14,595 bytes in 257 blocks
==6057== still reachable: 42,154 bytes in 572 blocks
==6057== suppressed: 0 bytes in 0 blocks
==6057== Rerun with --leak-check=full to see details of leaked memory
==6057==
==6057== For counts of detected and suppressed errors, rerun with: -v
==6057== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
/home/dan/
Value of: result.succeeded()
Actual: false
Expected: true
client terminate error=process:
/home/dan/
Actual function call count doesn't match EXPECT_
Expected: to be called once
Actual: never called - unsatisfied and active
==6056==
==6056== HEAP SUMMARY:
==6056== in use at exit: 440 bytes in 10 blocks
==6056== total heap usage: 3,439 allocs, 3,429 frees, 257,864 bytes allocated
==6056==
==6056== LEAK SUMMARY:
==6056== definitely lost: 0 bytes in 0 blocks
==6056== indirectly lost: 0 bytes in 0 blocks
==6056== possibly lost: 130 bytes in 4 blocks
==6056== still reachable: 310 bytes in 6 blocks
==6056== suppressed: 0 bytes in 0 blocks
==6056== Rerun with --leak-check=full to see details of leaked memory
==6056==
==6056== For counts of detected and suppressed errors, rerun with: -v
==6056== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
/home/dan/
Value of: result.succeeded()
Actual: false
Expected: true
process:
[ FAILED ] BespokeDisplayS
Related branches
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 12 lines (+2/-0)1 file modifiedtests/integration-tests/test_drm_auth_magic.cpp (+2/-0)
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 1930 lines (+953/-456)24 files modifiedexamples/CMakeLists.txt (+3/-0)
examples/demo_client_display_config.c (+212/-0)
examples/eglapp.c (+10/-0)
examples/eglapp.h (+4/-0)
include/server/mir/frontend/session_mediator.h (+9/-9)
include/server/mir/shell/mediating_display_changer.h (+8/-1)
include/test/mir_test/stub_server_tool.h (+8/-8)
include/test/mir_test/test_protobuf_client.h (+1/-0)
include/test/mir_test_framework/cross_process_sync.h (+3/-0)
src/client/mir_connection.cpp (+44/-19)
src/client/mir_connection.h (+1/-0)
src/server/default_server_configuration.cpp (+2/-1)
src/server/frontend/session_mediator.cpp (+3/-1)
src/server/graphics/gbm/gbm_display.cpp (+40/-36)
src/server/shell/mediating_display_changer.cpp (+23/-3)
src/shared/protobuf/mir_protobuf.proto (+1/-1)
tests/acceptance-tests/CMakeLists.txt (+2/-0)
tests/acceptance-tests/test_display_configuration.cpp (+413/-0)
tests/integration-tests/test_display_info.cpp (+0/-333)
tests/mir_test_framework/cross_process_sync.cpp (+10/-0)
tests/unit-tests/client/test_mir_connection.cpp (+71/-13)
tests/unit-tests/frontend/test_protobuf_communicator.cpp (+1/-1)
tests/unit-tests/frontend/test_session_mediator.cpp (+9/-2)
tests/unit-tests/shell/test_mediating_display_changer.cpp (+75/-28)
summary: |
- integration-tests: BespokeDisplayServerTestFixture failing under - valgrind + valgrind integration-tests: [ FAILED ] BespokeDisplayServerTestFixture.* |
Changed in mir: | |
milestone: | none → 0.0.10 |
status: | Fix Committed → Fix Released |
Very frustrating. This bug has now vanished on *both* the machines I saw it on yesterday. I have tried bisecting and can't even reproduce it with older revisions.
Perhaps system updates resolved something...