View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0013780

CMake

CTest

public

2012-12-07 17:27

2016-06-10 14:31

Reporter

Frank U. May

Assigned To

Kitware Robot

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

moved

Platform

OS Version

Product Version

CMake 2.8.10.2

Target Version

Fixed in Version

Summary

0013780: Continuous ctest does not work if executed in individual steps

Description

When running CTest continuous in individual steps every step following ContinuousUpdate is skipped.

Basically it is a nice feature that continuous tests don't run, if there are no updates. However, it seems the current implementation breaks running continuous tests in individual steps.

ContinuousUpdate works fine and reports the update. All following steps just report the site and the build name and do nothing else.

Steps To Reproduce

1.) Set up a CTest environment updating from a repository (I am using Git).

2.) From workspace A push an update to the repository.

3.) From workspace B run:
   ctest -C Release -D ContinuousStart
   ctest -C Release -D ContinuousUpdate
   ctest -C Release -D ContinuousConfigure
   ctest -C Release -D ContinuousBuild
   ctest -C Release -D ContinuousSubmit

4.) Note that "ContinuousUpdate" properly reports the update, while the following steps do nothing but report site and build name.

5.) Same issue, if you try:
   ctest -C Release --track Continuous -D Experimental[ALL_STEPS]

6.) Same issue if you try:
   ctest -C Release --track "Continuous Master" -D Continuous[ALL_STEPS]

7.) Same issue if you try:
   ctest -C Release --track "Continuous Master" -D Experimental[ALL_STEPS]

8.) Workaround: it works, if you try:
   ctest -C Release --track "Commit Master" -D Experimental[ALL_STEPS]

Additional Information

As I am running continuous tests from my Git repository hook, the latter is a feasible workaround. But it is not nice at all; I would highly appreciate, if this could be fixed. Or if someone could point out, where I am showing off to be a dumb user. ;)

To me it seems that the information that there was indeed an update from the repository gets lost between ContinuousUpdate and the following steps.

Tags

No tags attached.

Attached Files

Relationships

Notes
(0042167) 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-12-07 17:27	Frank U. May	New Issue
2016-06-10 14:28	Kitware Robot	Note Added: 0042167
2016-06-10 14:28	Kitware Robot	Status	new => 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