diff options
author | David Cole <david.cole@kitware.com> | 2010-06-13 15:02:27 (GMT) |
---|---|---|
committer | David Cole <david.cole@kitware.com> | 2010-06-13 15:02:27 (GMT) |
commit | 199e7f2f331aded0c7cb3f666bd2c996e2b4aa5e (patch) | |
tree | 85a80af59237299195fae79d46a25cb60b7fc3e3 /Tests/ObjC++ | |
parent | 8d29fa46abba732410147aa80cbcc58ceb265835 (diff) | |
download | CMake-199e7f2f331aded0c7cb3f666bd2c996e2b4aa5e.zip CMake-199e7f2f331aded0c7cb3f666bd2c996e2b4aa5e.tar.gz CMake-199e7f2f331aded0c7cb3f666bd2c996e2b4aa5e.tar.bz2 |
Remove CTestTest3.
At this point, CTestTest3 causes more problems than it's worth.
It uses CVS to grab a remote (over the network) copy of kwsys
code for testing. This causes some sort of problem nearly every
night on the nightly CMake dashboards. Worse: it causes problems
on different machines on different nights, then the next day, it's
fine again. So: remove this test and monitor the coverage.
If we lose a significant portion of code coverage, I will revert
this commit and re-activate the test. However, if we do not lose
a significant portion of code coverage, I will remove the code
for the test as well as removing it from the CMakeLists.txt file.
Brad King and I discussed this over the last few weeks, and we both
think we have sufficient coverage of all the checkout and update code
in other locally (non-network) based tests.
On the other hand, even if we do take a mild hit on coverage temporarily,
it should be relatively easy to increase our coverage again by adding
bits to those other locally based tests.
Diffstat (limited to 'Tests/ObjC++')
0 files changed, 0 insertions, 0 deletions