Same problem or a different type of testfail?

19:54:42 [ RUN      ] ClientLatency.dropping_latency_is_closer_to_zero_than_one
19:54:42 [2017-01-31 19:54:42.347490] mirserver: Starting
19:54:42 [2017-01-31 19:54:42.347814] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
19:54:42 [2017-01-31 19:54:42.365959] mirserver: Using software cursor
19:54:42 [2017-01-31 19:54:42.378848] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
19:54:42 [2017-01-31 19:54:42.379166] mirserver: Mir version 0.26.0
19:54:42 [2017-01-31 19:54:42.387115] mirserver: Initial display configuration:
19:54:42 [2017-01-31 19:54:42.387331] mirserver:   Output 1: HDMI-A connected, 
used
19:54:42 [2017-01-31 19:54:42.387422] mirserver:       Physical size 0.0" 0x0mm
19:54:42 [2017-01-31 19:54:42.387506] mirserver:       Power is on
19:54:42 [2017-01-31 19:54:42.387580] mirserver:       Current mode 1920x1080 
60.00Hz
19:54:42 [2017-01-31 19:54:42.387647] mirserver:       Preferred mode 1920x1080 
60.00Hz
19:54:42 [2017-01-31 19:54:42.387710] mirserver:       Orientation normal
19:54:42 [2017-01-31 19:54:42.387786] mirserver:       Logical size 1920x1080
19:54:42 [2017-01-31 19:54:42.387887] mirserver:       Logical position +0+0
19:54:44 
/<<BUILDDIR>>/mir-0.26.0+xenial3900bzr3541/tests/acceptance-tests/test_latency.cpp:376:
 Failure
19:54:44 Value of: average_latency
19:54:44 Expected: is < 0.5
19:54:44   Actual: 0.50877 (of type float)
19:54:44 [  debug   ] 97 frames sampled, averaging 0.509 frames latency
19:54:44 [  debug   ]  0:  1.00  1.00  0.50  0.50  0.06  0.07  0.07  0.07  0.08 
 0.08
19:54:44 [  debug   ] 10:  0.08  0.08  0.25  0.25  0.12  0.10  0.17  0.08  0.04 
 0.25
19:54:44 [  debug   ] 20:  0.20  0.50  0.09  0.33  1.00  0.50  1.00  1.00  1.00 
 1.00
19:54:44 [  debug   ] 30:  1.00  1.00  1.00  1.00  1.00  0.50  0.12  0.11  3.00 
 0.04
19:54:44 [  debug   ] 40:  0.10  0.14  2.00  1.00  0.17  0.50  0.50  0.33  0.33 
 0.25
19:54:44 [  debug   ] 50:  0.08  0.07  0.07  0.08  0.07  0.08  0.33  0.33  1.00 
 0.20
19:54:44 [  debug   ] 60:  1.00  0.11  0.17  0.33  1.00  0.11  0.06  0.33  0.50 
 0.11
19:54:44 [  debug   ] 70:  0.11  0.04  0.04  0.07  0.04  0.07  0.06  0.04  0.33 
 2.00
19:54:44 [  debug   ] 80:  2.00  0.50  0.50  1.00  1.00  2.00  1.00  1.00  2.00 
 1.00
19:54:44 [  debug   ] 90:  0.14  1.00  0.14  0.50  0.14  0.04  1.00
19:54:44 [2017-01-31 19:54:44.472992] mirserver: Stopping
19:54:44 [  FAILED  ] ClientLatency.dropping_latency_is_closer_to_zero_than_one 
(2234 ms)

in the same run:
19:54:48 [ RUN      ] 
ClientLatency.async_swap_dropping_latency_is_closer_to_zero_than_one
19:54:48 [2017-01-31 19:54:48.485202] mirserver: Starting
19:54:48 [2017-01-31 19:54:48.485592] mirserver: Selected driver: 
mir:stub-graphics (version 0.26.0)
19:54:48 [2017-01-31 19:54:48.507703] mirserver: Using software cursor
19:54:48 [2017-01-31 19:54:48.524831] mirserver: Selected input driver: 
mir:stub-input (version: 0.26.0)
19:54:48 [2017-01-31 19:54:48.525074] mirserver: Mir version 0.26.0
19:54:48 [2017-01-31 19:54:48.535165] mirserver: Initial display configuration:
19:54:48 [2017-01-31 19:54:48.535282] mirserver:   Output 1: HDMI-A connected, 
used
19:54:48 [2017-01-31 19:54:48.535320] mirserver:       Physical size 0.0" 0x0mm
19:54:48 [2017-01-31 19:54:48.535344] mirserver:       Power is on
19:54:48 [2017-01-31 19:54:48.535369] mirserver:       Current mode 1920x1080 
60.00Hz
19:54:48 [2017-01-31 19:54:48.535393] mirserver:       Preferred mode 1920x1080 
60.00Hz
19:54:48 [2017-01-31 19:54:48.535411] mirserver:       Orientation normal
19:54:48 [2017-01-31 19:54:48.535431] mirserver:       Logical size 1920x1080
19:54:48 [2017-01-31 19:54:48.535449] mirserver:       Logical position +0+0
19:54:50 
/<<BUILDDIR>>/mir-0.26.0+xenial3900bzr3541/tests/acceptance-tests/test_latency.cpp:451:
 Failure
19:54:50 Value of: average_latency
19:54:50 Expected: is < 0.5
19:54:50   Actual: 0.664058 (of type float)
19:54:50 [  debug   ] 98 frames sampled, averaging 0.664 frames latency
19:54:50 [  debug   ]  0:  0.11  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08 
 0.08
19:54:50 [  debug   ] 10:  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08  0.08 
 0.08
19:54:50 [  debug   ] 20:  0.08  0.09  0.06  0.08  0.09  0.14  0.50  0.33  0.05 
 0.03
19:54:50 [  debug   ] 30:  1.00  1.00  2.00  1.00  0.33  0.11  0.10  0.14  0.50 
 1.00
19:54:50 [  debug   ] 40:  1.00  1.00  0.50  1.00  2.00  1.00  1.00  1.00  2.00 
 0.14
19:54:50 [  debug   ] 50:  0.11  2.00  1.00  1.00  1.00  1.00  1.00  1.00  1.00 
 2.00
19:54:50 [  debug   ] 60:  1.00  1.00  0.17  0.10  0.50  1.00  2.00  0.33  2.00 
 2.00
19:54:50 [  debug   ] 70:  1.00  0.09  0.17  0.50  1.00  1.00  2.00  1.00  0.33 
 0.06
19:54:50 [  debug   ] 80:  0.50  1.00  2.00  2.00  1.00  0.33  2.00  0.25  0.07 
 0.10
19:54:50 [  debug   ] 90:  1.00  2.00  1.00  0.09  0.17  1.00  1.00  0.33
19:54:50 [2017-01-31 19:54:50.852240] mirserver: Stopping
19:54:50 [  FAILED  ] 
ClientLatency.async_swap_dropping_latency_is_closer_to_zero_than_one (2420 ms)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1640366

Title:
  [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one (AKA
  dropping_latency_is_closer_to_zero_than_one)

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  20:35:16 10: [ RUN      ] ClientLatency.dropping_latency_is_limited_to_one
  20:35:16 10: [2016-11-08 20:35:16.713374] mirserver: Starting
  20:35:16 10: [2016-11-08 20:35:16.713544] mirserver: Selected driver: 
mir:stub-graphics (version 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.714686] mirserver: Using software cursor
  20:35:16 10: [2016-11-08 20:35:16.733467] mirserver: Initial display 
configuration:
  20:35:16 10: [2016-11-08 20:35:16.734637] mirserver: Selected input driver: 
mir:stub-input (version: 0.25.0)
  20:35:16 10: [2016-11-08 20:35:16.734766] mirserver: Mir version 0.25.0
  20:35:18 10: 
/<<BUILDDIR>>/mir-0.25.0+yakkety2807bzr3804/tests/acceptance-tests/test_latency.cpp:341:
 Failure
  20:35:18 10: Value of: max_latency
  20:35:18 10: Expected: is <= 1
  20:35:18 10:   Actual: 2 (of type unsigned int)
  20:35:18 10: [  debug   ] 98 frames sampled, averaging 1.0 frames latency
  20:35:18 10: [  debug   ]  0:  1  1  1  1  1  1  1  2  1  1
  20:35:18 10: [  debug   ] 10:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 20:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 30:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 40:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 50:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 60:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 70:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 80:  1  1  1  1  1  1  1  1  1  1
  20:35:18 10: [  debug   ] 90:  1  1  1  1  1  1  1  1
  20:35:18 10: [2016-11-08 20:35:18.575646] mirserver: Stopping
  20:35:18 10: [  FAILED  ] ClientLatency.dropping_latency_is_limited_to_one 
(1879 ms)

  [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2781/consoleFull]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1640366/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to