Mir

unit-tests SwitchingBundleTest takes too long for a unit test

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

Bug Description

$ bin/unit-tests --gtest_filter=-SwitchingBundleTest* | grep ====
[==========] Running 492 tests from 106 test cases.
[==========] 492 tests from 106 test cases ran. (791 ms total)
$ bin/unit-tests --gtest_filter=SwitchingBundleTest* | grep ====
[==========] Running 21 tests from 1 test case.
[==========] 21 tests from 1 test case ran. (16381 ms total)

This is because the code under test, and the test itself accesses the high resolution clock directly instead of using TimeSource and mocks.

Related branches

Changed in mir:
status: New → Triaged
importance: Undecided → Medium
Changed in mir:
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.0.11

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

This bug was fixed in the package mir - 0.0.10+13.10.20130903-0ubuntu1

---------------
mir (0.0.10+13.10.20130903-0ubuntu1) saucy; urgency=low

  [ Daniel van Vugt ]
  * SwitchingBundle: Simplify and clarify guarantees that
    compositor_acquire always has a buffer to return without blocking or
    throwing an exception. The trade-off is that to enforce the
    guarantee we need to permanently reserve one buffer for compositing.
    This reduces the flexibility of SwitchingBundle a little, such that
    minimum nbuffers is now 2. This was originally requested by
    Alexandros, as the potential throw concerned him. Although, it was
    logically guaranteed to never happen for other reasons. The second
    reason for doing this is to eliminate recycling logic, which while
    safe and correct, was quite confusing. So this change further proves
    that that logic (now removed) is not to blame for frame ordering
    bugs. .

  [ Christopher James Halse Rogers ]
  * Synthesise an unfocused event on destruction of a focused window We
    probably need to rethink focus entirely, but this is an incremental
    improvement that I need.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 1049
 -- Ubuntu daily release <email address hidden> Tue, 03 Sep 2013 14:04:56 +0000

Changed in mir (Ubuntu):
status: New → Fix Released
Changed in mir:
milestone: none → 0.0.11
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

Remote bug watches

Bug watches keep track of this bug in other bug trackers.