[ RUN ] ADBusEventLoop.handles_reply_timeouts DEBUG delay=99878419 in ms=99, lbound=100 /tmp/buildd/unity-system-compositor-0.0.5+15.04.20150430bzr237pkg0wily5/tests/integration-tests/test_dbus_event_loop.cpp:235: Failure Value of: delay Expected: is >= 8-byte object <64-00 00-00 00-00 00-00> Actual: 8-byte object <13-06 F4-05 00-00 00-00> [ FAILED ] ADBusEventLoop.handles_reply_timeouts (107 ms)
Ok, the measured delay is just under the timeout. Which could be because the timeout is enqueued (and therefore could initiate) before noting the start time.
[ RUN ] ADBusEventLoop. handles_ reply_timeouts unity-system- compositor- 0.0.5+15. 04.20150430bzr2 37pkg0wily5/ tests/integrati on-tests/ test_dbus_ event_loop. cpp:235: Failure handles_ reply_timeouts (107 ms)
DEBUG delay=99878419 in ms=99, lbound=100
/tmp/buildd/
Value of: delay
Expected: is >= 8-byte object <64-00 00-00 00-00 00-00>
Actual: 8-byte object <13-06 F4-05 00-00 00-00>
[ FAILED ] ADBusEventLoop.
Ok, the measured delay is just under the timeout. Which could be because the timeout is enqueued (and therefore could initiate) before noting the start time.