CDash of kdelibs
david.cole at kitware.com
Wed Jul 20 21:09:10 BST 2011
2011/7/20 Alexander Neundorf <neundorf at kde.org>
> Dave, if you find some time, could you please have a look at the issue
> whether it behaves as it should with using CTEST_USE_LAUNCHERS ?
> A link to a dashboard before and the new one with the launchers are below.
> On Wednesday 20 July 2011, Rolf Eike Beer wrote:
> > Am Dienstag, 19. Juli 2011, 09:03:17 schrieb Volker Krause:
> > > On Monday 18 July 2011 21:21:36 Alexander Neundorf wrote:
> > > > Volker, are you still doing "make Nightly" ?
> > >
> > > well, something inbetween I guess, manual ctest calls but not using the
> > > script in quality.
> > >
> > > > If so, this is quite limited and has a bootstrapping problem.
> > > > Did you consider using the ctest scripts in svn in quality/ ?
> > >
> > > That didn't exist back when I set up this build (it's running for more
> > > than 1.5 years now) I think :)
> > Whatever you did two days ago it made things worse IMHO. There is the
> I wouldn't say it got worse.
> Here you see the compile commands and I actually didn't see an occasion
> warnings for multiple files were mixed into one entry:
> You also see the command which was invoked
> Not quite sure why it considers
> "Generating parts.moc" a warning. Adding this to the exceptions regexp
> help here.
> The number of warnings changed from 2400 to 300, this seems a bit much.
> Here is the "old" build:
> I think there is some size limit for the submission to cdash (which is IIRC
> configurable). Maybe with the new format it is more data and so stuff has
> cut ?
It looks ok to me.
The 2400 was lines of warnings that match the regexes. The 300 is: there
were warnings in that many invocations of the compiler. (i.e. if there are
100 warnings in a single C++ source file, it will only show up as 1 on the
dashboard) Before, the measurement was number of warnings themselves, with
launchers on, it's number of files with warnings.
The "Generating parts.moc" is considered a "warning" because there is output
even though the exit condition is 0. (At least, I think that's what it
Let me know if you suspect something specific is incorrect.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kde-core-devel