Mir

CI is not running mir_performance_tests for desktop architectures: amd64/i386

Bug #1566743 reported by Daniel van Vugt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Triaged
Medium
Unassigned
mir (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

CI is not running mir_performance_tests (and others - e.g. the smoke tests) on all architectures

I think...
https://code.launchpad.net/~vanvugt/mir/this-should-fail-1/+merge/291081

Tags: performance
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

  #

Fails for the expected reason too?

08:42:20 + phablet-test-run -x -s JB011018 -v sudo /usr/bin/mir_performance_tests
08:42:20 running sudo /usr/bin/mir_performance_tests
08:42:20 Running main() from main.cpp
08:42:20 [==========] Running 1 test from 1 test case.
08:42:20 [----------] Global test environment set-up.
08:42:20 [----------] 1 test from GLMark2Test
08:42:20 [ RUN ] GLMark2Test.fullscreen_default
08:42:20 [2016-04-06 08:42:20.454578] mirplatform: Found graphics driver: mir:android (version 0.22.0)
08:42:20 [2016-04-06 08:42:20.456125] mirplatform: Found graphics driver: mir:mesa-kms (version 0.22.0)
08:42:20 [2016-04-06 08:42:20.457692] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.22.0)
08:42:20 [2016-04-06 08:42:20.458406] mirplatform: Found graphics driver: throw-on-creation (version 0.22.0)
08:42:20 [2016-04-06 08:42:20.458540] mirplatform: Found graphics driver: dummy (version 0.22.0)
08:42:20 libevdev error in fix_invalid_absinfo: BUG: Device "mtk-tpd" has invalid ABS_MT_TRACKING_ID rangeSaving GLMark2 detailed results to: /tmp/GLMark2Test_fullscreen_default.log
08:42:31 ../../../tests/performance-tests/test_glmark2-es2-mir.cpp:101: Failure
08:42:31 Value of: run_glmark2("--fullscreen")
08:42:31 Expected: is >= 9999999
08:42:31 Actual: 69 (of type int)
08:42:31 [ FAILED ] GLMark2Test.fullscreen_default (10783 ms)
08:42:31 [----------] 1 test from GLMark2Test (10784 ms total)
08:42:31
08:42:31 [----------] Global test environment tear-down
08:42:31 [==========] 1 test from 1 test case ran. (10784 ms total)
08:42:31 [ PASSED ] 0 tests.
08:42:31 [ FAILED ] 1 test, listed below:
08:42:31 [ FAILED ] GLMark2Test.fullscreen_default
08:42:31
08:42:31 1 FAILED TEST
08:42:31  YOU HAVE 5 DISABLED TESTS

https://mir-jenkins.ubuntu.com/job/device-runtests-mir/device_type=krillin/397/consoleFull

Changed in mir:
status: New → Invalid
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I don't know where you got that from, but we still have a problem if it's not easily findable in:
https://code.launchpad.net/~vanvugt/mir/this-should-fail-1/+merge/291081

Also, _all_ achitectures should be failing on a faulty performance test. And they're not.

Changed in mir:
status: Invalid → New
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

I agree it could be easier to find the output from test failures, but that's not what this report is about. It could be raised separately?

We've never run the performance tests on _all_ architectures. In the past (pre-jenkaas) the test machines didn't have graphics support. I've not checked if that has changed.

So, this is a request for enhancement?

description: updated
summary: - [regression] CI is no longer running mir_performance_tests
+ CI is not running mir_performance_tests (et alia) on all architectures
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It's worth noting that most of our mir_performance_tests only work with the mesa platform, not android (due to android-specific bugs). So to run them only on android means most of mir_performance_tests are never being run at all.

summary: - CI is not running mir_performance_tests (et alia) on all architectures
+ CI is not running mir_performance_tests for desktop architectures:
+ amd64/i386
tags: removed: regression
Changed in mir:
status: New → Triaged
tags: added: performance
Revision history for this message
Michał Sawicz (saviq) wrote :

Syncing task from Mir.

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