Mir

integration tests are outputting (too many) DisplayServer log messages

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

Bug Description

Further to bug 1394221, tests are still outputting (too many) internal log messages:

[----------] 4 tests from DemoPrivateProtobuf
[ RUN ] DemoPrivateProtobuf.client_calls_server
[1420618801.421818] (II) DisplayServer: Mir version 0.10.0 <=======
[ OK ] DemoPrivateProtobuf.client_calls_server (26 ms)
[ RUN ] DemoPrivateProtobuf.wrapping_message_processor
[1420618801.442053] (II) DisplayServer: Mir version 0.10.0 <=======
[ OK ] DemoPrivateProtobuf.wrapping_message_processor (18 ms)
[ RUN ] DemoPrivateProtobuf.server_receives_function_call
[1420618801.466653] (II) DisplayServer: Mir version 0.10.0 <=======
[ OK ] DemoPrivateProtobuf.server_receives_function_call (29 ms)
[ RUN ] DemoPrivateProtobuf.client_receives_result
[1420618801.500652] (II) DisplayServer: Mir version 0.10.0 <=======
[ OK ] DemoPrivateProtobuf.client_receives_result (32 ms)
[----------] 4 tests from DemoPrivateProtobuf (108 ms total)

[----------] 2 tests from SurfaceLoop
[ RUN ] SurfaceLoop.all_created_buffers_are_destroyed
[1420618801.538223] (II) DisplayServer: Mir version 0.10.0
[ OK ] SurfaceLoop.all_created_buffers_are_destroyed (60 ms)
[ RUN ] SurfaceLoop.all_created_buffers_are_destroyed_if_client_disconnects_without_releasing_surfaces
[1420618801.601339] (II) DisplayServer: Mir version 0.10.0
[ OK ] SurfaceLoop.all_created_buffers_are_destroyed_if_client_disconnects_without_releasing_surfaces (64 ms)
[----------] 2 tests from SurfaceLoop (125 ms total)

[----------] 2 tests from StaleFrames
[ RUN ] StaleFrames.are_dropped_when_restarting_compositor
[1420618801.670529] (II) DisplayServer: Mir version 0.10.0
[ OK ] StaleFrames.are_dropped_when_restarting_compositor (264 ms)
[ RUN ] StaleFrames.only_fresh_frames_are_used_after_restarting_compositor
[1420618801.939657] (II) DisplayServer: Mir version 0.10.0
[ OK ] StaleFrames.only_fresh_frames_are_used_after_restarting_compositor (270 ms)
[----------] 2 tests from StaleFrames (543 ms total)

Related branches

Changed in mir:
milestone: 0.10.0 → 0.11.0
summary: - Tests are outputting (too many) log messages
+ Tests are outputting (too many) DisplayServer log messages
description: updated
description: updated
Changed in mir:
milestone: 0.11.0 → none
status: In Progress → Triaged
assignee: Daniel van Vugt (vanvugt) → nobody
summary: - Tests are outputting (too many) DisplayServer log messages
+ integration tests are outputting (too many) DisplayServer log messages
Changed in mir:
milestone: none → 0.11.0
status: Triaged → In Progress
assignee: nobody → Alan Griffiths (alan-griffiths)
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.11.0

Changed in mir:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.2 KiB)

This bug was fixed in the package mir - 0.11.0+15.04.20150209.1-0ubuntu1

---------------
mir (0.11.0+15.04.20150209.1-0ubuntu1) vivid; urgency=medium

  [ Daniel van Vugt ]
  * New upstream release 0.11.0 (https://launchpad.net/mir/+milestone/0.11.0)
    - Enhancements:
      . Lots more major plumbing in the Android code, on the path to
        supporting external displays.
      . Add support for clang 3.6.
      . Major redesign of server classes in mir::shell,scene and friends
        (still in progress).
      . Added client API for creating dialogs and tooltips.
      . Added new surface states: mir_surface_state_hidden and
        mir_surface_state_horizmaximized.
      . Performance: Use optimally efficient fragment shading when possible.
      . Performance: (Desktop) Composite using double buffering instead of
        triple to reduce visible lag.
      . mir_proving_server: Can now resize windows from any edge or corner
        using the existing Alt+middlebuttondrag.
      . mir_proving_server: Added some demo custom shaders (negative and
        high contrast modes: Super+N/C).
      . mir_proving_server: Can now close clients politely via Alt+F4.
      . Added MirPointerInputEvent (part of the new input API, the old
        MirMotionEvent is still supported also for now).
    - ABI summary: Servers need rebuilding, but clients do not;
      . Mirclient ABI unchanged at 8
      . Mircommon ABI unchanged at 3
      . Mirplatform ABI bumped to 6
      . Mirserver ABI bumped to 29
    - Bug fixes:
      . [regression] mir_demo_server exits immediately with boost
        bad_any_cast exception (LP: #1414630)
      . need way to position menus and tooltips (relative positioning to
        parent) (LP: #1324101)
      . GLibMainLoopTest failure seen in CI (LP: #1413748)
      . Clang builds fail in CI (LP: #1416317)
      . segfault in mir::compositor::GLProgramFamily::Shader::init()
        (LP: #1416482)
      . GLRenderer: The default fragment shader is sub-optimal for alpha=1.0
        (LP: #1350674)
      . mesa::DisplayBuffer::post_update is triple buffered - more laggy than
        it needs to be (LP: #1350725)
      . Cannot connect to nested server when started from a differen vt
        (LP: #1379266)
      . [testfail] AsioMainLoopAlarmTest fails in CI (LP: #1392256)
      . Compositor report inconsistently reports frame time during bypass,
        and render time otherwise (LP: #1408906)
      . [regression] mir_demo_client_fingerpaint doesn't paint anything any
        more (with the mouse) (LP: #1413139)
      . Hardware cursor is always slightly ahead of the composited image
        (LP: #1274408)
      . integration tests are outputting (too many) DisplayServer log
        messages (LP: #1408231)
      . [regression] deploy-and-test.sh doesn't work any more (unless you
        have umockdev installed already) (LP: #1413479)
      . Color Inverse on display. Toggle Negative Image (LP: #1400580)
      . mir-ubuntu-vivid-armhf-ci fails consistently (LP: #1407863)
      . Double-buffered surfaces may lag or freeze if event driven and not
        constantly redrawing (LP: #1395581)
      . Pointer motion and crossing events...

Read more...

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

Other bug subscribers