Merge lp:~timo-jyrinki/click-update-manager/fix_qt52_use_qpa_platform_minimal into lp:click-update-manager

Proposed by Timo Jyrinki
Status: Merged
Approved by: dobey
Approved revision: 39
Merged at revision: 38
Proposed branch: lp:~timo-jyrinki/click-update-manager/fix_qt52_use_qpa_platform_minimal
Merge into: lp:click-update-manager
Diff against target: 12 lines (+1/-1)
1 file modified
CMakeLists.txt (+1/-1)
To merge this branch: bzr merge lp:~timo-jyrinki/click-update-manager/fix_qt52_use_qpa_platform_minimal
Reviewer Review Type Date Requested Status
dobey (community) Approve
PS Jenkins bot (community) continuous-integration Approve
Review via email: mp+202461@code.launchpad.net

Commit message

Use xvfb -screen 0 640x480x24 for running tests. (LP: #1271172)

Description of the change

Similar changes are being done in all packages needing it, like http://bazaar.launchpad.net/~system-settings-touch/gsettings-qt/trunk/revision/43

To post a comment you must log in.
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :
review: Approve (continuous-integration)
Revision history for this message
dobey (dobey) wrote :

There is absolutely no information in the bug that describes the problem, or why this would fix it. Please provide that information.

review: Needs Information
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :
Revision history for this message
dobey (dobey) wrote :

What does setting the platform to "minimal" actually do there? Would not adding "-screen 0 640x480x24" to the xvfb-run args list, be a better fix?

Or if we should use "minimal" for platform, should we not do this in the build system rather than debian/rules, and remove the use of xvfb-run?

Changes like this, we should do always or never; not only in debian/rules.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

The minimal plugin avoids using X while still allowing QML tests to be run and doing the rendering, just not the final stage of outputting to X. Some tests may be hard to run without accelerated OpenGL since QML2 requires OpenGL 2.0 / shaders etc. But a PPA test shows that your suggested method also works, and it might be better since there's a X virtual framebuffer in the picture. Changing the proposal to that.

39. By Timo Jyrinki

Use xvfb -screen 0 640x480x24 instead of minimal platform plugin

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :
review: Approve (continuous-integration)
Revision history for this message
dobey (dobey) :
review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
=== modified file 'CMakeLists.txt'
--- CMakeLists.txt 2013-10-14 11:33:57 +0000
+++ CMakeLists.txt 2014-01-24 06:34:13 +0000
@@ -18,7 +18,7 @@
18${CMAKE_INSTALL_DATADIR}/icons FILES_MATCHING PATTERN *.png)18${CMAKE_INSTALL_DATADIR}/icons FILES_MATCHING PATTERN *.png)
1919
20add_custom_target(check20add_custom_target(check
21 COMMAND xvfb-run -a qmltestrunner -input ${CMAKE_CURRENT_SOURCE_DIR}/tests/unit21 COMMAND xvfb-run -s '-screen 0 640x480x24' -a qmltestrunner -input ${CMAKE_CURRENT_SOURCE_DIR}/tests/unit
22)22)
2323
24add_subdirectory(tests/autopilot)24add_subdirectory(tests/autopilot)

Subscribers

People subscribed via source and target branches