5.27.0: test suite is failing in two uits
Looks like two units are failing
+ xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu --output-on-failure --force-new-ctest-process -j48 ' '
Internal ctest changing into directory: /home/tkloczko/rpmbuild/BUILD/kscreen-5.27.0/x86_64-redhat-linux-gnu
Test project /home/tkloczko/rpmbuild/BUILD/kscreen-5.27.0/x86_64-redhat-linux-gnu
Start 1: kscreen-kded-testgenerator
Start 2: kscreen-kded-configtest
Start 3: kscreen-kded-osdtest
1/3 Test #3: kscreen-kded-osdtest .............***Failed 0.02 sec
Error calling osdService:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kscreen.osdService was not provided by any .service files")
2/3 Test #2: kscreen-kded-configtest ..........***Failed 0.05 sec
********* Start testing of TestConfig *********
Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.0.1 20230127 (Red Hat 13.0.1-0)), fedora 39
PASS : TestConfig::initTestCase()
PASS : TestConfig::testSimpleConfig()
QWARN : TestConfig::testTwoScreenConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
PASS : TestConfig::testTwoScreenConfig()
QWARN : TestConfig::testRotatedScreenConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
PASS : TestConfig::testRotatedScreenConfig()
QWARN : TestConfig::testDisabledScreenConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
QWARN : TestConfig::testDisabledScreenConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
FAIL! : TestConfig::testDisabledScreenConfig() Compared values are not the same
Actual (output->isEnabled()): 1
Expected (false) : 0
Loc: [/home/tkloczko/rpmbuild/BUILD/kscreen-5.27.0/tests/kded/configtest.cpp(208)]
PASS : TestConfig::testConfig404()
QWARN : TestConfig::testCorruptConfig() kscreen.kded: Failed to find a matching output in the current info data - this means that our info is corrupted or a different device with the same serial number has been connected (very unlikely).
QWARN : TestConfig::testCorruptConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
QWARN : TestConfig::testCorruptConfig() kscreen.kded: Failed to find a matching output in the current info data - this means that our info is corrupted or a different device with the same serial number has been connected (very unlikely).
QWARN : TestConfig::testCorruptConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
PASS : TestConfig::testCorruptConfig()
QWARN : TestConfig::testCorruptEmptyConfig() kscreen.kded: Failed to find a matching output in the current info data - this means that our info is corrupted or a different device with the same serial number has been connected (very unlikely).
QWARN : TestConfig::testCorruptEmptyConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
QWARN : TestConfig::testCorruptEmptyConfig() kscreen.kded: Failed to find a matching output in the current info data - this means that our info is corrupted or a different device with the same serial number has been connected (very unlikely).
QWARN : TestConfig::testCorruptEmptyConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
PASS : TestConfig::testCorruptEmptyConfig()
QWARN : TestConfig::testCorruptUselessConfig() kscreen.kded: Failed to find a matching output in the current info data - this means that our info is corrupted or a different device with the same serial number has been connected (very unlikely).
QWARN : TestConfig::testCorruptUselessConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
PASS : TestConfig::testCorruptUselessConfig()
SKIP : TestConfig::testNullConfig() crashes
Loc: [/home/tkloczko/rpmbuild/BUILD/kscreen-5.27.0/tests/kded/configtest.cpp(257)]
PASS : TestConfig::testIdenticalOutputs()
SKIP : TestConfig::testMoveConfig() crashes
Loc: [/home/tkloczko/rpmbuild/BUILD/kscreen-5.27.0/tests/kded/configtest.cpp(393)]
QWARN : TestConfig::testFixedConfig() kscreen.kded: Failed to find a matching mode - this means that our config is corrupted or a different device with the same serial number has been connected (very unlikely). Falling back to preferred modes.
QWARN : TestConfig::testFixedConfig() kscreen.kded: UPower not available, lid detection won't work
QWARN : TestConfig::testFixedConfig() kscreen.kded: PowerDevil SuspendSession action not available!
PASS : TestConfig::testFixedConfig()
PASS : TestConfig::cleanupTestCase()
Totals: 11 passed, 1 failed, 2 skipped, 0 blacklisted, 8ms
********* Finished testing of TestConfig *********
3/3 Test #1: kscreen-kded-testgenerator ....... Passed 0.08 sec
33% tests passed, 2 tests failed out of 3
Total Test time (real) = 0.09 sec
The following tests FAILED:
2 - kscreen-kded-configtest (Failed)
3 - kscreen-kded-osdtest (Failed)
Errors while running CTest