make[2]: Entering directory '/var/tmp/portage/sys-fs/xwmfs-0.81/work/xwmfs-0.81/tests' make[3]: Entering directory '/var/tmp/portage/sys-fs/xwmfs-0.81/work/xwmfs-0.81/tests' FAIL: test_name_update.py FAIL: test_events.py ============================================================================ Testsuite summary for xwmfs 0.81 ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 13.0-desktop_abi32+64-test_20171029-135004 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-6.4.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) [5] pypy (fallback) java-config: The following VMs are available for generation-2: 1) IcedTea JDK 7.2.6.11 [icedtea-7] 2) IcedTea JDK 3.6.0 [icedtea-8] 3) IcedTea JDK 7.2.6.11 [icedtea-bin-7] *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-7 [2] icedtea-8 [3] icedtea-bin-7 [4] icedtea-bin-8 system-vm emerge -qpv sys-fs/xwmfs [ebuild N ] sys-fs/xwmfs-0.81
Created attachment 502962 [details] emerge-info.txt
Created attachment 502964 [details] emerge-history.txt
Created attachment 502966 [details] environment
Created attachment 502968 [details] etc.portage.tbz2
Created attachment 502970 [details] logs.tbz2
Created attachment 502972 [details] sys-fs:xwmfs-0.81:20171107-013514.log
Created attachment 502974 [details] temp.tbz2
Created attachment 502976 [details] tests.tbz2
The tests require a DISPLAY to work. They're more tailored towards interactive testing. I'll make a new upstream release to skip tests if DISPLAY isn't available so the error should go away.
Use virtx.eclass to provide an Xvfb environment for the tests.
(In reply to Michał Górny from comment #10) > Use virtx.eclass to provide an Xvfb environment for the tests. Thanks for the tip. I don't think it's worth the hassle though. The tests have additional dependencies like 'xterm' and are also prone to race conditions. So running them automatically is likely to result in spurious errors.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6822fb6672769e8f0246a1ea4f3a16611633db1d commit 6822fb6672769e8f0246a1ea4f3a16611633db1d Author: Matthias Gerstner <Matthias.Gerstner@nefkom.net> AuthorDate: 2017-11-08 20:26:34 +0000 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: 2017-11-30 14:46:34 +0000 sys-fs/xwmfs: version bump to 0.82. Closes: https://bugs.gentoo.org/636814 Closes: https://github.com/gentoo/gentoo/pull/6180 Package-Manager: Portage-2.3.8, Repoman-2.3.3 sys-fs/xwmfs/Manifest | 1 + sys-fs/xwmfs/xwmfs-0.82.ebuild | 20 ++++++++++++++++++++ 2 files changed, 21 insertions(+)
