On 07/24/2015 10:23 AM, Matthias Kretz wrote:
set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON")
Is that in your ctest -S script?
Do you also have set(CTEST_USE_LAUNCHERS ON) in the same script?
Nils
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://
On Friday 24 July 2015 10:23:48 Matthias Kretz wrote:
> set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON")
>
> I don't get any output on the CDash dashboard anymore. AFAICT the Build
> directory in Testing/tag/ is removed but never recreated. I.e. if I call
Maybe the better lead:
I made the UseLauncher
OK, this patch is bogus. Because
cmCTestBuildHandler::LaunchHelper::LaunchHelper should call MakeDirectory
already if this->Handler->UseCTestLaunch is true.
Makes my test results even more strange then.
On Friday 24 July 2015 11:28:13 Matthias Kretz wrote:
> On Friday 24 July 2015 10:23:48 Matt
On Friday 24 July 2015 10:23:48 Matthias Kretz wrote:
> set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON")
>
> I don't get any output on the CDash dashboard anymore. AFAICT the Build
> directory in Testing/tag/ is removed but never recreated.
With the following patch I get output back to the dashboard:
Hi,
using
set(ENV{CTEST_USE_LAUNCHERS_DEFAULT} "ON")
I don't get any output on the CDash dashboard anymore. AFAICT the Build
directory in Testing/tag/ is removed but never recreated. I.e. if I call
CTEST_LAUNCH_LOGS=./not-existing-directory make
the launcher output is not stored to disk.
On 11/09/2011 06:06 PM, EXT-York, Gantry wrote:
> I'm looking for suggestions from someone who has used CTest to report results
> to a dashboard other than CDash.
>
> I'd like to be able to simply type
>
> gmake test TESTOPTS="-report"
>
> then have CTest traverse all the directories and run th
I'm looking for suggestions from someone who has used CTest to report results
to a dashboard other than CDash.
I'd like to be able to simply type
gmake test TESTOPTS="-report"
then have CTest traverse all the directories and run the defined tests. Not
only would I like it to run these tests,
Hello,
I'm trying to use ctest with multiple CTestConfig.cmake files.
When I have a single CTestConfig.cmake in my code root directory, and run :
ctest -D Experimental
Ctest runs and submit results correctly.
Now when I move this file, let's say into C:\dir\myCTestConfig.cmake , and
I do the following to run tests for all built archs on OS X:
# --
macro(MXA_ADD_TEST testname Exename)
if (NOT APPLE)
ADD_TEST(${testname} ${Exename})
else()
foreach(arch ${CMAKE_OSX_ARCHITECTURES})
hi all,
i am trying to run ctest with the qemu cpu emulator: so if i am compiling a
test
case myTest, it is usually simply called with `./myTest'.
is it possible to wrap this into a program, so that it calls `qemu-ARCHITECTURE
-cpu CPUTYPE ./myTest'?
thanks, tim
--
t...@klingt.org
http://tim
Hello,
I have nearly succeeded moving a project from an autotools based system to a
CMake/CTest/CDash system. I must say I am impressed with CMake. I have two
questions though:
1) Is it possible for CTest to use a shell script which calls cmake? The
project depends on a dozen TPLs installe
I have discovered the problem, and it has nothing to do with CTest or
CMake. It had everything to do with our overly-complex build
system... but I now understand more about CTest/Dart etc than I did,
so thanks for your time!
___
Powered by www.kitware.c
We do have a CTestConfig.cmake:
set(CTEST_PROJECT_NAME "BRAINS3")
set(CTEST_NIGHTLY_START_TIME "00:00:00 EST")
set(CTEST_DROP_METHOD "http")
set(CTEST_DROP_SITE "testing.psychiatry.uiowa.edu")
set(CTEST_DROP_LOCATION "/CDash/submit.php?project=BRAINS3")
set(CTEST_DROP_SITE_CDASH TRUE)
I ran the c
What are the contents of your CTestConfig.cmake file?
If you are going to run dashboards like this:
BUILD COMMAND runcmd ctest -V -D NightlyStart -D NightlyConfigure -D
NightlyBuild -D NightlyTest -D NightlySubmit
running: ctest -V -D NightlyStart -D NightlyConfigure -D NightlyBuild
-D NightlyTest
I'm now finding out that we had
include(Dart)
in all our Makefiles. I commented that out, and added
include(CTest)
instead. Then I deleted everything in the build directory, and
re-configured. I get these errors still:
/scratch/williamsnk/Testing/BRAINS-COMPILE/Linux/DEBUG-lib/CMake-build/bi
Are you doing:
include(CTest)
in your CMakeLists.txt file?
On Fri, Jun 4, 2010 at 10:51 AM, kent williams wrote:
> We don't have Dart installed on some machines we want to do testing
> on. Consequently including Dart.cmake does nothing to generate
> DartConfiguration.tcl.
>
> If you're not usin
We don't have Dart installed on some machines we want to do testing
on. Consequently including Dart.cmake does nothing to generate
DartConfiguration.tcl.
If you're not using Dart, how do you set things up such that you avoid
this error?
running: ctest -V -D NightlyStart -D NightlyConfigure -D Nig
Hi,
We're learning that CTest is a very useful tool with a rich set of
options. So rich in fact that it's a bit confusing just exactly what
CTest does for the various
(Experimental|Nightly)..(Setup|Config|Build|Test|...) I see of of
this is controlled by the CMake generated entries in the D
Is there any way to get the --build-config value passed into ctest to be used
as a variable in an add_test() command? I would like to chain that down to
another ctest call which is doing --build-and-test on a sub-target. Naturally,
that sub-build is building the wrong configuration, and on mac
Hi,
I'm using CTest to submit my own Dart2 Server. The project that I'm
testing is using qmake (not CMake, sorry).
If I write a DartConfiguration.tcl file I can configure, build and
submit without any problem. But now I'm trying to write a CTest script
like this:
SET (CTEST_SOURCE_DIRECTORY ".")
20 matches
Mail list logo
