View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0013137

CMake

CTest

public

2012-04-16 10:48

2016-06-10 14:31

Reporter

Olivier Pierard

Assigned To

Kitware Robot

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

moved

Platform

x86_64

Suse

OS Version

10.3

Product Version

CMake-2-8

Target Version

Fixed in Version

Summary

0013137: ctest_start(Model APPEND) should keep the initial track specified in first call to ctest_start

Description

I 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

Tags

No tags attached.

Attached Files

Relationships

Notes
(0030403) David Cole (manager) 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 (administrator) 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.

Issue History
Date Modified	Username	Field	Change
2012-04-16 10:48	Olivier Pierard	New Issue
2012-08-11 21:35	David Cole	Status	new => backlog
2012-08-11 21:35	David Cole	Note Added: 0030403
2016-06-10 14:28	Kitware Robot	Note Added: 0042028
2016-06-10 14:28	Kitware Robot	Status	backlog => resolved
2016-06-10 14:28	Kitware Robot	Resolution	open => moved
2016-06-10 14:28	Kitware Robot	Assigned To	=> Kitware Robot
2016-06-10 14:31	Kitware Robot	Status	resolved => closed