MantisBT - CMake
View Issue Details
0013583CMakeCTestpublic2012-10-10 10:102016-06-10 14:31
Clinton Stimpson 
Kitware Robot 
normalminoralways
closedmoved 
 
 
0013583: would like more info in cdash if the svn update command failed
ctest doesn't include the output of a failed svn update. So if it happens, I always have to dig in to see why.

Some possible scenarios for failure (some not so common - but I've encountered all of these):
- ssl certificate was renewed and needs to be accepted by the client
- internet connection is down for a moment
- access permissions are modified to exclude the client
- svn server is relocated
No tags attached.
related to 0015610closed Brad King ctest_update can fail without returning -1 as RETURN_VALUE 
Issue History
2012-10-10 10:10Clinton StimpsonNew Issue
2012-10-10 10:42Brad KingNote Added: 0031203
2012-10-10 11:46Clinton StimpsonNote Added: 0031204
2012-10-10 13:16Brad KingStatusnew => backlog
2015-06-11 09:12Clinton StimpsonRelationship addedrelated to 0015610
2016-06-10 14:28Kitware RobotNote Added: 0042131
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
(0031203)
Brad King   
2012-10-10 10:42   
CTest leaves detailed information on the client build tree in:

 Testing/Temporary/LastUpdate_$stamp.log

One could look at refactoring CTest to include the content of this log in Update.xml somewhere. CDash would also need to be taught to do something with it.
(0031204)
Clinton Stimpson   
2012-10-10 11:46   
Ah, thanks. I was looking in Update.xml and didn't see anything there.
This time it wasn't obvious, but from the LastUpdate*.log file I do see why.
(0042131)
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.