On Saturday, September 05, 2015 12:47:16 PM Matthias Heinz wrote: > Package: kglobalaccel > Version: 5.13.0 > Severity: normal > > --- Please enter the report below this line. --- > > Hi, > > I'm trying to test the patch for https://bugs.kde.org/show_bug.cgi?id=341959 > and installed the latest source for kglobalaccel. Build doing a plain, > unmodified build a build test keeps failing: > > ---- > Start 1: kglobalshortcuttest > 1/1 Test #1: kglobalshortcuttest ..............***Failed 8.05 sec > ********* Start testing of KGlobalShortcutTest ********* > Config: Using QtTest library 5.4.2, Qt 5.4.2 (x86_64-little_endian-lp64 > shared (dynamic) release build; by GCC 5.2.1 20150808) > PASS : KGlobalShortcutTest::initTestCase() > PASS : KGlobalShortcutTest::testSetShortcut() > FAIL! : KGlobalShortcutTest::testActivateShortcut() 'actionASpy.wait()' > returned FALSE. () > Loc: [../../autotests/kglobalshortcuttest.cpp(193)] > PASS : KGlobalShortcutTest::testFindActionByKey() > PASS : KGlobalShortcutTest::testChangeShortcut() > PASS : KGlobalShortcutTest::testStealShortcut() > PASS : KGlobalShortcutTest::testSaveRestore() > PASS : KGlobalShortcutTest::testListActions() > PASS : KGlobalShortcutTest::testComponentAssignment() > PASS : KGlobalShortcutTest::testConfigurationActions() > PASS : KGlobalShortcutTest::testNotification() > PASS : KGlobalShortcutTest::testGetGlobalShortcut() > PASS : KGlobalShortcutTest::testOverrideMainComponentData() > PASS : KGlobalShortcutTest::testForgetGlobalShortcut() > PASS : KGlobalShortcutTest::cleanupTestCase() > Totals: 14 passed, 1 failed, 0 skipped, 0 blacklisted > ********* Finished testing of KGlobalShortcutTest ********* > > > 0% tests passed, 1 tests failed out of 1 > > Total Test time (real) = 8.05 sec > > The following tests FAILED: > 1 - kglobalshortcuttest (Failed) > Errors while running CTest > > ---- > > Is this intended?
A normal package build does not run the tests [1], so this won't occur in the archive. I think troubleshooting this to find out if there's a problem in the package or in the upstream code is worthwhile, but I would also look into what's triggering the tests in your build system since we don't normally do that. [1] https://buildd.debian.org/status/fetch.php?pkg=kglobalaccel&arch=i386&ver=5.13.0-2&stamp=1441123332
