Bill Hoffman wrote:
Clemens Arth wrote:
Until now, this worked well, but now it seems that CTEST_RUN_SCRIPT
is only called once and, not as expected, multiple times one after
each other. I guess this is not the intended behaviour... Can anyone
reproduce this?
I reproduced it. I think I
Bill Hoffman wrote:
Clemens Arth wrote:
thanks for having a look at this issue. I get an error because I have
SET (CTEST_TRIGGER_SITE not used)
in my script, which causes an error in any case (resolving not
used). However, I think this is the default value to set if one does
not want
The bug fix allowing CTEST_DROP_SITE_CDASH to work was only recently made in
CVS CTest. It is not in 2.6.3
On Wed, Mar 4, 2009 at 12:11 PM, Clemens Arth clemens.a...@gmx.at wrote:
Bill Hoffman wrote:
Clemens Arth wrote:
thanks for having a look at this issue. I get an error because I
Well, it's on you to decide, but I'd still suggest that Bill's
workaround also goes into the cvs for the next release to make
everything more bullet-proof...
David Cole wrote:
The bug fix allowing CTEST_DROP_SITE_CDASH to work was only recently
made in CVS CTest. It is not in 2.6.3
On
Clemens Arth wrote:
Well, it's on you to decide, but I'd still suggest that Bill's
workaround also goes into the cvs for the next release to make
everything more bullet-proof...
I have already done the commit with the fix. For now, I would suggest
just letting it do something for the
Hi guys,
by now I was working with 2.6.2 and used a script to run multiple
builds/tests sequentially with the following structure:
snip
...
# run for the first time
SET(CTEST_SOURCE_DIRECTORY ${SOURCEROOTABS})
SET(CTEST_BINARY_DIRECTORY
