Nightly test runs from 2008-09-24_01:15:01
M Breugelmans
mbr.nxi at gmail.com
Wed Sep 24 08:54:06 UTC 2008
Interesting to see that all my integration tests fail (those with 'it'
in the name) . I can't reproduce that here on 2 different machines,
where/how do I get verbose output?
I think in time we also might want to include other kind of tests:
- performance tests to measure improvements.
- valgrind memcheck. I've got a python script that runs this on the
qtest & veritas unit tests, which could probably included with an
add_test. There's native support for valgrind as well somewhere in
ctest I think.
- (squish) gui tests
- fuzz/random tests. There's a duchain-include one which is in the
normal suite and a qtest-outputparser one which is a standalone
executable and currently not included (but should be)
[some more comments inline]
On Wed, Sep 24, 2008 at 3:17 AM, Andreas Pakulat <andreas at froglogic.com> wrote:
> ------------------------------------------------------------------------------
> Nightly unit test run results from 2008-09-24_01:15:01:
> ------------------------------------------------------------------------------
>
> KDevPlatform:
> **********************************************************
> [OUTPUT]
> Start processing tests
>
> [HANDLER_OUTPUT]
> Test project /home/andreas/src/kde4/build/kdevplatform
>
> 1/ 28 Testing sublime-areaoperationtest Passed
> 2/ 28 Testing sublime-areawalkertest Passed
> 3/ 28 Testing sublime-viewtest Passed
> 4/ 28 Testing sublime-documenttest Passed
> 5/ 28 Testing sublime-controllertest ***Failed
This is a failure I put in while I fixed all sublime tests. Basically,
as far as I could see, it was a QSKIP with a wrong comment. Shouldn't
be hard to make this right.
> 6/ 28 Testing sublime-viewactivationtest Passed
> 7/ 28 Testing sublime-aggregatemodeltest Passed
> 8/ 28 Testing sublime-toolviewtoolbartest Passed
> 9/ 28 Testing shell-documentoperationtest Passed
> 10/ 28 Testing shell-projectcontrollertest Passed
> 11/ 28 Testing shell-sessioncontrollertest Passed
> 12/ 28 Testing kdevcvs-test Passed
> 13/ 28 Testing veritas-ut-annotationmanager Passed
> 14/ 28 Testing veritas-ut-lcovinfoparser Passed
> 15/ 28 Testing veritas-ut-coveredfile Passed
> 16/ 28 Testing veritas-ut-reportmodel Passed
> 17/ 28 Testing veritas-ut-reportitems Passed
> 18/ 28 Testing veritas-ut-reportfileitem Passed
> 19/ 28 Testing kdevgit-test ***Failed
where's the bzr and hg tests?
> 20/ 28 Testing veritas-ut-test Passed
> 21/ 28 Testing veritas-ut-resultsmodel Passed
> 22/ 28 Testing veritas-ut-runnermodel Passed
> 23/ 28 Testing veritas-ut-resultsproxymodel Passed
> 24/ 28 Testing veritas-ut-runnerproxymodel Passed
> 25/ 28 Testing veritas-ut-testexecutor Passed
> 26/ 28 Testing veritas-it-runnerwindow ***Failed
> 27/ 28 Testing veritas-ut-selectionstoretest Passed
> 28/ 28 Testing veritas-ut-treetraverse Passed
>
> 89% tests passed, 3 tests failed out of 28
> [ERROR_MESSAGE]
>
> The following tests FAILED:
>
> [HANDLER_OUTPUT]
> 5 - sublime-controllertest (Failed)
>
> 19 - kdevgit-test (Failed)
> 26 - veritas-it-runnerwindow (Failed)
> [ERROR_MESSAGE]
> Errors while running CTest
> **********************************************************
>
> KDevelop:
> **********************************************************
> [OUTPUT]
> Start processing tests
>
> [HANDLER_OUTPUT]
> Test project /home/andreas/src/kde4/build/kdevelop
>
> 1/ 36 Testing parsertest Passed
> 2/ 36 Testing pooltest Passed
> 3/ 36 Testing cppexpressionparsertest Passed
> 4/ 36 Testing duchaintest Passed
> 5/ 36 Testing veritas-ut-classskeleton Passed
> 6/ 36 Testing veritas-ut-stubcreation ***Failed
Yea, I got that one too since a couple of days. Never touched anything
near the code in that period though. Since it relies heavily on the
c++ duchain it is probably a regression there (but I havent looked
into it).
> 7/ 36 Testing veritas-ut-constructorskeleton Passed
> 8/ 36 Testing veritas-ut-methodskeleton Passed
> 9/ 36 Testing veritas-ut-classwriter Passed
> 10/ 36 Testing veritas-ut-uutcreation Passed
> 11/ 36 Testing veritas-ut-ktextdocumentstub Passed
> 12/ 36 Testing veritas-ut-includewriter Passed
> 13/ 36 Testing cppcodecompletiontest Passed
> 14/ 36 Testing qtest-ut-qtestoutputparser Passed
> 15/ 36 Testing qtest-ut-qtestcase Passed
> 16/ 36 Testing qtest-ut-qtestcommand Passed
> 17/ 36 Testing qtest-ut-qtestsuite Passed
> 18/ 36 Testing qtest-ut-qtestregister Passed
> 19/ 36 Testing qtest-ut-qtestoutputmorpher Passed
> 20/ 36 Testing qtest-it-qtestrunnertest ***Failed
> 21/ 36 Testing qtest-ut-suitebuilder Passed
> 22/ 36 Testing qtest-ut-casebuilder Passed
> 23/ 36 Testing check-it-checkrunnertest ***Failed
> 24/ 36 Testing cmake-parsertest Passed
> 25/ 36 Testing cmakecompliance Passed
> 26/ 36 Testing cmake-astfactorytest Passed
> 27/ 36 Testing cmakeast-test ***Failed
> 28/ 36 Testing cmake-cmakecondition Passed
> 29/ 36 Testing cmakeduchaintest ***Failed
> 30/ 36 Testing cmakeprojectvisitortest Passed
> 31/ 36 Testing cmakeparserutilstest Passed
> 32/ 36 Testing qmake-parsetest Passed
> 33/ 36 Testing qmake-assignmenttest Passed
> 34/ 36 Testing qmake-functionscopetest ***Failed
> 35/ 36 Testing qmake-scopetest Passed
> 36/ 36 Testing qmake-lexertest Passed
>
> 83% tests passed, 6 tests failed out of 36
> [ERROR_MESSAGE]
>
> The following tests FAILED:
>
> [HANDLER_OUTPUT]
> 6 - veritas-ut-stubcreation (Failed)
>
> 20 - qtest-it-qtestrunnertest (Failed)
> 23 - check-it-checkrunnertest (Failed)
> 27 - cmakeast-test (Failed)
> 29 - cmakeduchaintest (Failed)
> 34 - qmake-functionscopetest (Failed)
> [ERROR_MESSAGE]
> Errors while running CTest
> **********************************************************
More information about the KDevelop-devel
mailing list