On Thursday 21 July 2011 21:44:48 Alexander Neundorf wrote:
> On Thursday 21 July 2011, Volker Krause wrote:
> > On Wednesday 20 July 2011 21:51:43 Alexander Neundorf wrote:
> > > Hi,
> > >
> > > Dave, if you find some time, could you please have a look at the issue
> > > here, whether it behaves
On Thursday 21 July 2011, Volker Krause wrote:
> On Wednesday 20 July 2011 21:51:43 Alexander Neundorf wrote:
> > Hi,
> >
> > Dave, if you find some time, could you please have a look at the issue
> > here, whether it behaves as it should with using CTEST_USE_LAUNCHERS ? A
> > link to a dashboard
2011/7/20 Alexander Neundorf
> Hi,
>
> Dave, if you find some time, could you please have a look at the issue
> here,
> 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
On Wednesday 20 July 2011 21:51:43 Alexander Neundorf wrote:
> Hi,
>
> Dave, if you find some time, could you please have a look at the issue here,
> 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.
>
> O
Hi,
Dave, if you find some time, could you please have a look at the issue here,
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 20
On Wednesday 20 July 2011 08:29:16 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
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 lim
On Monday 18 July 2011 21:21:36 Alexander Neundorf wrote:
> On Monday 18 July 2011, Rolf Eike Beer wrote:
> > Am Sonntag, 17. Juli 2011, 12:47:36 schrieb Rolf Eike Beer:
> > > When I look at the kdelibs test results at
> > > http://my.cdash.org/index.php?project=kdelibs I see the following things
>
On Monday 18 July 2011, Rolf Eike Beer wrote:
> Am Sonntag, 17. Juli 2011, 12:47:36 schrieb Rolf Eike Beer:
> > When I look at the kdelibs test results at
> > http://my.cdash.org/index.php?project=kdelibs I see the following things
> > that IMHO need to be changed:
> >
> > -the limit of 3000 warni
Am Sonntag, 17. Juli 2011, 12:47:36 schrieb Rolf Eike Beer:
> When I look at the kdelibs test results at
> http://my.cdash.org/index.php?project=kdelibs 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?
We don'
Am Sonntag 17 Juli 2011, 12:58:35 schrieben Sie:
> On Sunday 17 July 2011, Rolf Eike Beer wrote:
> > -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
On Sunday 17 July 2011, Rolf Eike Beer wrote:
> When I look at the kdelibs test results at
> http://my.cdash.org/index.php?project=kdelibs 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
When I look at the kdelibs test results at
http://my.cdash.org/index.php?project=kdelibs 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?
-the moc files are counted in the coverage results even if CTestConfig.cmak
13 matches
Mail list logo