Hello, this is your friendly unit test police...
On Friday 31 July 2015 13:29:53 no-re...@kde.org wrote:
> Build URL:
> https://build.kde.org/job/kdeclarative%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/22/
That one is a real test failure.
The "data" dir is missing.
Marco: I already emailed you about that a month ago, please please give this
the highest priority.
Unittests should always pass, otherwise they're useless.
13:29:34 2/2 Test #2: quickviewsharedengine ............***Failed 1.60 sec
13:29:34 ********* Start testing of QuickViewSharedEngineTest *********
13:29:34 Config: Using QtTest library 5.4.2, Qt 5.4.2
(x86_64-little_endian-lp64 shared (dynamic) debug build; by GCC 4.9.2)
13:29:34 FAIL! : QuickViewSharedEngineTest::initTestCase()
'!m_dataDirectory.isEmpty()' returned FALSE. ('data' directory not found)
13:29:34 Loc:
[/home/jenkins/builds/kdeclarative/kf5-qt5/autotests/util.cpp(61)]
13:29:34 PASS : QuickViewSharedEngineTest::cleanupTestCase()
13:29:34 Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted
13:29:34 ********* Finished testing of QuickViewSharedEngineTest *********
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
