MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008668CMakeCTestpublic2009-03-04 08:502010-12-14 18:49
ReporterRoscoe A. Bartlett 
Assigned ToZach Mullen 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in VersionCMake-2-8 
Summary0008668: CTest Dev: Missing exeutables shown as failed tests when using MPI
Description
This is not really a CTest defect per say but we have an issue where
when an MPI tests fails to build, CTest will still try to run it and
show it as 'Fail' instead of as 'NotRun' as shown, for example, by:

    http://trilinos-dev.sandia.gov/cdash/viewTest.php?onlyfailed&buildid=2506 [^]

The problem is that the initial executable is mpiexec, not our test
program so CTest thinks that the executable exists. In a serial
build, the executable that CTest sees is the actual executable and
therefore correctly shows these as 'NotRun' as shown, for example, by:

    http://trilinos-dev.sandia.gov/cdash/viewTest.php?buildid=2731 [^]

Is there some way to get CTest to realize what is really going on and
mark these tests as not run? Could CTest add something like an
EXEC_PREFIX_CMND argument or something that we could set to mpiexec
and all of its arguments that CTest would use when running the
executable? For example, you might have:


    ADD_TEST( myExecName
        myExecName.exe arg1 arg2 ...
        EXEC_PREFIX_CMND mpiexec -np 2
        )

In this way, if 'myExecName.exe' did not get built, CTest would realize that it could not run the test and would mark the test as 'NotRun'.

NOTE: This solution would not be specific to MPI.

This is not a high priority issue for Trilinos but it would be one of
our wants. I have not orgalized all of these little wants yet but we
can do that after the major issues are all resolved that are shown at:

    https://www.kitware.com/cmake-cdash-trilinos [^]

Bill had asked us to add these list of wants (i.e. the "icing" on the
cake) but I will wait until the main issues are resolved.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-04 08:50Roscoe A. BartlettNew Issue
2009-08-19 16:16Bill HoffmanStatusnew => assigned
2009-08-19 16:16Bill HoffmanAssigned To => Zach Mullen
2009-08-19 16:26Roscoe A. BartlettNote Added: 0017163
2009-12-07 14:08Zach MullenNote Added: 0018715
2009-12-07 14:09Zach MullenNote Deleted: 0018715
2009-12-10 15:40Zach MullenNote Added: 0018805
2009-12-10 15:40Zach MullenStatusassigned => resolved
2009-12-10 15:40Zach MullenFixed in Version => CMake-2-8
2009-12-10 15:40Zach MullenResolutionopen => fixed
2010-12-14 18:49David ColeNote Added: 0024064
2010-12-14 18:49David ColeStatusresolved => closed

Notes
(0017163)
Roscoe A. Bartlett   
2009-08-19 16:26   
Instead of what I listed above, I would rather have a DEPENDENCIES target property that you could set to define a set of files that have to exist in order to run a test.
(0018805)
Zach Mullen   
2009-12-10 15:40   
Just checked in code to add the requested option. Use SET_TESTS_PROPERTIES with the REQUIRED_FILE property.
(0024064)
David Cole   
2010-12-14 18:49   
Closing bugs that have been resolved for more than 3 months without any further updates.