MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013169CMakeCTestpublic2012-04-25 14:282016-06-10 14:31
ReporterAlex Rettig 
Assigned ToKitware Robot 
PrioritylowSeveritytweakReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013169: Internal misconfiguration leads to weird error messages: "Cannot create directory /Testing/Temporary"
DescriptionWhen calling "ctest_submit" under certain circumstances, the following error message shows up:

Cannot create directory /Testing/Temporary
Cannot create log file: LastSubmit.log


 
Steps To ReproduceIn a unix shell do:

>% echo 'ctest_submit( FILES ctesttest.ctest )' > ctesttest.ctest
>% ctest -S ctesttest.ctest

If you do

>% ctest --debug -S ctesttest.ctest

the output gives the first hint where to start searching:
.../cmake-2.8.8/Source/cmCTest.cxx:899 Cannot create directory /Testing/Temporary
Additional InformationReading cmCTest.cxx shows, that the member this->BinaryDir seems not to be initialized correctly (which is used as prefix in testingDir in .../cmake-2.8.8/Source/cmCTest.cxx:899) .

Neither cmCTest::Initialize() nor cmCTest::UpdateCTestConfiguration() seem to get called to do the initialisation of this->BinaryDir when ctest is run in the described way. For me it looks weird, that cmCTest::Initialize() is called in only one case in cmCTest::Run() (line 2440) of nested if statements, but I didn't try to understand this code in detail.

While this doesn't seem to do any harm in my use case it points to a bug which may have more annoying effects in other cases.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-04-25 14:28Alex RettigNew Issue
2012-06-29 09:35Bjoern ThielNote Added: 0029864
2012-06-29 09:36Bjoern ThielNote Edited: 0029864bug_revision_view_page.php?bugnote_id=29864#r715
2012-08-11 21:42David ColeStatusnew => backlog
2012-08-11 21:42David ColeNote Added: 0030454
2016-06-10 14:28Kitware RobotNote Added: 0042035
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
(0029864)
Bjoern Thiel   
2012-06-29 09:35   
(edited on: 2012-06-29 09:36)
Right. And if on one (windows) machine representing several clients /Testing/Temporary/LastSubmit.log can be created the corresponding logs overwrite each other. I'd appreciate this being fixed.
(0030454)
David Cole   
2012-08-11 21:42   
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.
(0042035)
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.