The following issue has been SUBMITTED. ====================================================================== http://public.kitware.com/Bug/view.php?id=13780 ====================================================================== Reported By: Frank U. May Assigned To: ====================================================================== Project: CMake Issue ID: 13780 Category: CTest Reproducibility: always Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2012-12-07 17:27 EST Last Modified: 2012-12-07 17:27 EST ====================================================================== Summary: 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. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2012-12-07 17:27 Frank U. May New Issue ====================================================================== -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
