MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013137CMakeCTestpublic2012-04-16 10:482016-06-10 14:31
ReporterOlivier Pierard 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
Platformx86_64OSSuseOS Version10.3
Product VersionCMake-2-8 
Target VersionFixed in Version 
Summary0013137: ctest_start(Model APPEND) should keep the initial track specified in first call to ctest_start
DescriptionI recently spent some time in solving an obvious problem which could be easily avoided.

In a CTest script, I do a first ctest_start(ModelName TRACK cdash_track_name), ctest_build then run another ctest script on a node of our cluster which starts with ctest_start(ModelName APPEND) and then ctest_test.

Unfortunately, the track is not kept. This sounds logical to keep information given in the first ctest_start. Another coherent solution would be to define a variable 'CTEST_TRACK' which would be automatically used in a ctest_start as already done for CTEST_SOURCE_DIRECTORY.
Steps To Reproduce* First ctest_script contains:

ctest_start(ModelName TRACK cdash_track_name)
ctest_configure(BUILD "CTEST_BINARY_DIRECTORY")

* Second ctest_script contains:

ctest_start(ModelName)
ctest_test(BUILD "CTEST_BINARY_DIRECTORY")

Results of configure step will be sent to cdash_track_name track on the CDash while second is sent to the usual 'Nightly' track
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-04-16 10:48Olivier PierardNew Issue
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030403
2016-06-10 14:28Kitware RobotNote Added: 0042028
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030403)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0042028)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.