CDash of kdelibs

Alexander Neundorf neundorf at
Sun Jul 17 11:58:35 BST 2011

On Sunday 17 July 2011, Rolf Eike Beer wrote:
> When I look at the kdelibs test results at
> I see the following things
> that IMHO need to be changed:
> -the limit of 3000 warnings is reached, do we need to increase the limit?

I don't think having more then 3000 warnings there is useful.
From my own experience the display of warnings starts to be useful when it's 
close to zero, let's say less than 20 or so.
Then you start to see whether new warnings appeared, and can check if that 
With such a huge number as we have now this doesn't make a lot of sense in my 
So, we should try to get that number down.
Either by fixing them, or by disabling the wanrings, or by putting the ones we 
are not interested in the the exception regex for ignored warnings.

> -the moc files are counted in the coverage results even if
> CTestConfig.cmake contains
> set(CTEST_CUSTOM_COVERAGE_EXCLUDE ".moc$" "moc_" "ui_")
> So something is wrong there. This also adds to the number of warnings as
> the first to warning messages are "no relevant classes found" ones which
> should be suppressed.
> IIRC those lines need to be moved to the CTestCustom.cmake to take effect.
> Alex?

I think so.

> -I think that all testcases should also be removed from the coverage
> results, i.e. those list should be extended by "/tests/".

Shouldn't the coverage for the testcases itself be around 100%, so they don't 
cause fixing work.
Beside that I don't have an opinion whether they should be included or not.


More information about the kde-core-devel mailing list