Mir

unit-tests:ApplicationSession are noisy (lots of GMOCK WARNING)

Bug #1390312 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Low
Daniel van Vugt
mir (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

unit-tests:ApplicationSession are noisy (lots of GMOCK WARNING) ...

$ bin/mir_unit_tests --gtest_filter="ApplicationSession.*"
Running main() from command_line_server_configuration.cpp
Note: Google Test filter = ApplicationSession.*
[==========] Running 13 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 13 tests from ApplicationSession
[ RUN ] ApplicationSession.create_and_destroy_surface

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: add_observer(@0x7fff473d0200 16-byte object <E0-0C C3-03 00-00 00-00 D0-0C C3-03 00-00 00-00>)
Stack trace:

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: remove_surface(@0x7fff473d0200 16-byte object <F0-FB C2-03 00-00 00-00 E0-FB C2-03 00-00 00-00>)
Stack trace:
[ OK ] ApplicationSession.create_and_destroy_surface (1 ms)
[ RUN ] ApplicationSession.listener_notified_of_surface_destruction_on_session_destruction

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: add_observer(@0x7fff473d01f0 16-byte object <70-0D C3-03 00-00 00-00 60-0D C3-03 00-00 00-00>)
Stack trace:

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: remove_surface(@0x7fff473d01f0 16-byte object <F0-FB C2-03 00-00 00-00 E0-FB C2-03 00-00 00-00>)
Stack trace:

Related branches

Changed in mir:
importance: Undecided → Low
status: New → Triaged
Changed in mir:
milestone: none → 0.9.0
assignee: nobody → Daniel van Vugt (vanvugt)
status: Triaged → In Progress
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.9.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir (Ubuntu):
importance: Undecided → Low
status: New → In Progress
status: In Progress → Triaged
Changed in mir:
status: Fix Committed → Fix Released
Changed in mir (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers