qtmir fails a test against Qt 5.4.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtmir (Ubuntu) |
Fix Released
|
High
|
Albert Astals Cid |
Bug Description
Interestingly one test fails in qtmir when built against Qt 5.4.1 - does it rely on some sort of bug that got fixed?
Some changelogs:
- https:/
- https:/
^ dummy plug-in no longer built on Linux, "generic" to be used?
Build logs:
https:/
https:/
---
3/11 Test #3: Screen, .......
Running main() from gtest_main.cc
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from ScreenTest
[ RUN ] ScreenTest.
/build/
Value of: screen-
Actual: false
Expected: true
[ FAILED ] ScreenTest.
[----------] 1 test from ScreenTest (5 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (6 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] ScreenTest.
1 FAILED TEST
qtmir.sensor: Screen - nativeOrientation is: 1
qtmir.sensor: Screen - initial currentOrientation is: 1
---
See information about Qt 5.4.1 landing at https:/
All Qt 5.4.1 bugs https:/
Related branches
- Gerry Boland (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Michał Sawicz: Approve (code)
-
Diff: 14 lines (+5/-0)1 file modifiedtests/mirserver/Screen/screen_test.cpp (+5/-0)
description: | updated |
description: | updated |
Changed in qtmir (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in qtmir (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Albert Astals Cid (aacid) |
Orientation seems to work fine on the phone, so this might be something that only affects builder machines and maybe would need some mocking?