qt.qpa.screen: QXcbConnection: Could not connect to display Could not connect to any X display. make[3]: *** [Makefile:510: check] Error 1 make[3]: Leaving directory '/var/tmp/portage/app-admin/qtpass-1.2.2/work/QtPass-1.2.2/tests/auto/util' make[2]: *** [Makefile:348: sub-util-check] Error 2 make[2]: Leaving directory '/var/tmp/portage/app-admin/qtpass-1.2.2/work/QtPass-1.2.2/tests/auto' ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_test_20180513-102141 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv app-admin/qtpass [ebuild N ] app-admin/qtpass-1.2.2 USE="{test}"
Created attachment 531804 [details] emerge-info.txt
Created attachment 531806 [details] app-admin:qtpass-1.2.2:20180516-112544.log
Created attachment 531808 [details] emerge-history.txt
Created attachment 531810 [details] environment
Created attachment 531812 [details] etc.portage.tbz2
Created attachment 531814 [details] temp.tbz2
Created attachment 531816 [details] tests.tbz2
> QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/root/run', please create it with 0700 permissions. > qt.qpa.screen: QXcbConnection: Could not connect to display > Could not connect to any X display. You need X server to run tests. It works fine for me under root: > export DISPLAY=:0 > xhost + Should I support somehow this in ebuild? Mention in ebuild a necessity to have X server to run a test? Disable test that requires X server?
Like I mentioned in you pull request you can use virtualx.eclass Look for examples in the tree, it's very easy to use. try setting VIRTUALX_REQUIRED="test", inherit virtualx and adding src_test() { virtx default }
I definitely should use it with one exception: There is no need setting VIRTUALX_REQUIRED="test", since this is a default value: # @ECLASS-VARIABLE: VIRTUALX_REQUIRED # @DESCRIPTION: # Variable specifying the dependency on xorg-server and xhost. # Possible special values are "always" and "manual", which specify # the dependency to be set unconditionaly or not at all. # Any other value is taken as useflag desired to be in control of # the dependency (eg. VIRTUALX_REQUIRED="kde" will add the dependency # into "kde? ( )" and add kde into IUSE. : ${VIRTUALX_REQUIRED:=test} Thank you for pointing me on virtualx.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5bd9e9a3b9ba3c633fcc724caa2b358808ca8b1c commit 5bd9e9a3b9ba3c633fcc724caa2b358808ca8b1c Author: Vladimir Pavljuchenkov (SpiderX) <spiderx@spiderx.dp.ua> AuthorDate: 2018-06-17 18:57:48 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2018-06-21 14:51:40 +0000 app-admin/qtpass: version bump to 1.2.3 fix test stage (wrt #655896) Closes: https://bugs.gentoo.org/655896 Closes: https://github.com/gentoo/gentoo/pull/8879 Package-Manager: Portage-2.3.40, Repoman-2.3.9 app-admin/qtpass/Manifest | 1 + app-admin/qtpass/qtpass-1.2.3.ebuild | 63 ++++++++++++++++++++++++++++++++++++ 2 files changed, 64 insertions(+)
