Re: [PATCH 17/24] gnu: kwidgetsaddons: Fix test failure.

[David Craven]

> Might (setenv "QT_QPA_PLATFORM" "offscreen") also be enough?

Interesting, that also fixes the problem, but causes a new one...

********* Start testing of KDualActionTest *********
Config: Using QtTest library 5.7.0, Qt 5.7.0
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC
4.9.3)
PASS   : KDualActionTest::initTestCase()
PASS   : KDualActionTest::testSetGuiItem()
FAIL!  : KDualActionTest::testSetIconForStates() Compared pointers are
not the same
   Actual   (action.inactiveIcon()): (nil)
   Expected (icon)                 : 0x65a4d0
   Loc: 
[/tmp/guix-build-kwidgetsaddons-5.24.0.drv-0/kwidgetsaddons-5.24.0/autotests/kdualactiontest.cpp(56)]
PASS   : KDualActionTest::testSetActive()
PASS   : KDualActionTest::testTrigger()
PASS   : KDualActionTest::cleanupTestCase()
Totals: 5 passed, 1 failed, 0 skipped, 0 blacklisted, 3ms
********* Finished testing of KDualActionTest *********

>  Starting an Xvfb server and then not stopping it again is kinda ... extreme.

Since the tests are run in a container, I'd expect all processes started inside
the container to receive a sigterm when the container is (shutdown?).

> Also, who says that :1 is free?

Again since the tests are run in a container, I'd expect that there
isn't a xserver
running unless I explicitly start it.

Are my assumptions wrong?
Do you think it's worth tracking down the test failure when my solution works?