Mir

  1. Bug #1640366
  2. Comment #2

Comment 2 for bug 1640366

Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one

Again:

04:08:00 12: /<<BUILDDIR>>/mir-0.25.0+yakkety2810bzr3811/tests/acceptance-tests/test_latency.cpp:341: Failure
04:08:00 12: Value of: max_latency
04:08:00 12: Expected: is <= 1
04:08:00 12: Actual: 2 (of type unsigned int)
04:08:00 12: [ debug ] 98 frames sampled, averaging 1.0 frames latency
04:08:00 12: [ debug ] 0: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 10: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 20: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 30: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 40: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 50: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 60: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 70: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 80: 1 1 1 1 1 1 1 1 1 1
04:08:00 12: [ debug ] 90: 1 1 1 2 1 1 1 1
04:08:00 12: [2016-11-09 04:08:00.110391] mirserver: Stopping
04:08:00 12: [ FAILED ] ClientLatency.dropping_latency_is_limited_to_one (1821 ms)

https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=yakkety/2784/consoleFull