summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Modules: Fix spelling 'To distributed' -> 'To distribute'Todd Gamblin2010-08-092-2/+2
|
* Merge topic 'fix-CTestTestFailedSubmit-xmlrpc'Brad King2010-08-031-0/+1
|\ | | | | | | | | fbe67a9 CTestTestFailedSubmit-xmlrpc: Pass with "Submission problem"
| * CTestTestFailedSubmit-xmlrpc: Pass with "Submission problem"Modestas Vainius2010-07-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | Pass the test when there is "Submission problem" in the output. This is at least applicable to XMLRPC. Full error message is below: ------ Submission problem: Curl failed to perform HTTP POST request. curl_easy_perform() says: <url> malformed (-504) . Problems when submitting via XML-RPC ------
* | Merge topic 'fix-cmake-self-references'Brad King2010-08-032-7/+7
|\ \ | | | | | | | | | | | | df1e00f Refer to self with CMake_(SOURCE|BINARY)_DIR (#10046)
| * | Refer to self with CMake_(SOURCE|BINARY)_DIR (#10046)Brad King2010-07-292-7/+7
| |/ | | | | | | | | This is good practice, and is necessary to support building CMake as a subdirectory of another project.
* | Merge topic 'ctest-git-flexibility'Brad King2010-08-031-0/+5
|\ \ | |/ |/| | | | | | | | | a7319cf ctest_update: Run 'git submodule' at top level 7bf8dc1 ctest_update: Support ".git file" work trees 65cb72f ctest_update: Abort if Git FETCH_HEAD has no candidates
| * ctest_update: Support ".git file" work treesBrad King2010-07-261-0/+5
| | | | | | | | | | | | | | Commit c3781efb (Support Git upstream branch rewrites, 2010-06-08) assumed that ".git/FETCH_HEAD" exists inside the source tree. Fix the implementation to handle a work tree using a ".git file" to link to its repository. Use "git rev-parse --git-dir" to locate the real .git dir.
* | Merge topic 'resolve/doc-spelling/CPackRPM'Brad King2010-07-201-1/+1
|\ \ | | | | | | | | | | | | | | | 7739d78 Merge CPackRPM changes into doc-spelling 9203e91 Fix spelling errors reported by Lintian.
| * \ Merge CPackRPM changes into doc-spellingBrad King2010-07-131-6/+57
| |\ \ | | | | | | | | | | | | | | | | Conflicts: Modules/CPackRPM.cmake
| * | | Fix spelling errors reported by Lintian.Kai Wasserbäch2010-07-131-1/+1
| | | | | | | | | | | | | | | | | | | | During a Lintian run on the binary packages of CMake in Debian I was notified of many spelling mistakes.
* | | | Merge topic 'resolve/ctest-file-checksum/remove-CTestTest3'Brad King2010-07-132-0/+39
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 38c762c Merge 'remove-CTestTest3' into ctest-file-checksum 46df0b4 Activate retry code on any curl submit failure. 8705497 Checksum test should use CMAKE_TESTS_CDASH_SERVER d0d1cdd Mock checksum failure output for old CDash versions af5ef0c Testing for CTest checksum 86e81b5 CTest should resubmit in the checksum failed case d6b7107 Fix subscript out of range crash 082c87e Cross-platform fixes for checksum/retry code e525649 Checksums on CTest submit files, and retry timed out submissions.
| * \ \ \ Merge 'remove-CTestTest3' into ctest-file-checksumBrad King2010-07-1317-72/+454
| |\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: Tests/CMakeLists.txt
| * | | | | Checksum test should use CMAKE_TESTS_CDASH_SERVERZach Mullen2010-06-221-0/+5
| | | | | |
| * | | | | Testing for CTest checksumZach Mullen2010-06-103-1/+35
| | | | | |
| * | | | | Checksums on CTest submit files, and retry timed out submissions.Zach Mullen2010-06-031-1/+1
| | | | | |
* | | | | | Merge topic 'external-project-launcher'Brad King2010-07-131-0/+6
|\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b2634b6 Detect CMake warnings and errors in build output. 012c986 ExternalProject: Add LOG_* options to hide step output
| * | | | | | ExternalProject: Add LOG_* options to hide step outputBrad King2010-06-211-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Optionally hide the output of each external project build step by wrapping its command in a launcher script. Make output available in log files instead. This simplifies the output of external project builds.
* | | | | | | Add another expected output for the failed submit tests.David Cole2010-07-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The CTestTestFailedSubmit-http test was failing on the hut11 Experimental dashboards with "Empty reply from server" due to a localhost settings change.
* | | | | | | Fix cycle detection for test dependenciesZach Mullen2010-06-309-1/+116
| |_|_|_|/ / |/| | | | |
* | | | | | CheckSourceTree test: read UpdateCommand from Update.xml.David Cole2010-06-271-6/+57
| |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If GIT_EXECUTABLE is not passed in, and is not available from DartConfiguration.tcl or CTestConfiguration.ini, then make one more last ditch attempt to get it from Update.xml, if there is an Update.xml. For dashboards that have successfully done a ctest_update call, there should be an Update.xml in the Testing subdir of the binary tree. Parse that file for the git executable recorded in the <UpdateCommand> element. And make this test pass on those RogueResearch dashboard machines!
* | | | | Merge branch 'ctest-git-empty-commits'Brad King2010-06-241-2/+18
|\ \ \ \ \
| * | | | | CTest: Parse empty Git commits correctlyBrad King2010-06-231-2/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Git's diff-tree format has no '\n'-terminated blank line at the end of its commit message body block if there are no diff lines. Instead the message body is terminated by '\0' and there is no diff section. Teach CTest to parse the format in this case.
* | | | | | Parallel CTest hangs if serial test has dependsZach Mullen2010-06-231-0/+2
|/ / / / /
* | | | | Look in the ctest ini file for GitCommand.David Cole2010-06-211-0/+54
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | If GIT_EXECUTABLE is not passed into the test, but the source tree is a git checkout, then use GitCommand or UpdateCommand from the ctest ini file to set its value. Presumably, a dashboard running the test suite had to have set this properly in order to do the ctest_update step.
* | | | Merge branch 'remove-CTestTest3'Brad King2010-06-151-13/+0
|\ \ \ \ | | |/ / | |/| |
| * | | Remove CTestTest3.David Cole2010-06-131-13/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | Merge branch 'ctest-git-flexibility'Brad King2010-06-157-27/+68
|\ \ \ \ | | |_|/ | |/| |
| * | | ctest_update: Support Git upstream branch rewritesBrad King2010-06-083-2/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use 'git fetch' followed by 'git reset' to update the source tree. This is better than 'git pull' because it can handle a rewritten upstream branch and does not leave local modifications. After fetch, parse FETCH_HEAD to find the merge head that 'git pull' would choose to track the upstream branch. Then reset to the selected head. In the normal fast-forward case the behavior remains unchanged. However, now local modifications and commits will be erased, and upstream rewrites are handled smoothly. This ensures that the upstream branch is tested as expected.
| * | | ctest_update: Support custom Git update commandBrad King2010-06-081-9/+44
| | | | | | | | | | | | | | | | | | | | Define CTest configuration variable CTEST_GIT_UPDATE_CUSTOM to set a custom command line for updating Git-managed source trees.
| * | | Generalize CTest.Update* test dashboard script helpersBrad King2010-06-086-16/+16
| |/ / | | | | | | | | | | | | | | | | | | Teach (create|run)_dashboard_script macros to treat the argument as the name of a build tree. Append '.cmake' to generate the dashboard script name. This allows future re-use of the macros for multiple test scripts.
* | | Merge branch 'msys-bootstrap-test'Brad King2010-06-152-5/+15
|\ \ \
| * | | Enable BootstrapTest on MSYSBrad King2010-06-112-5/+15
| |/ / | | | | | | | | | | | | | | | The bootstrap script works under MSYS, so test it. Use a launcher batch file since 'ctest --build-and-test' is a Windows program and will not honor the shebang line in the script.
* | | Run CTest.NoNewline test using built CMakeBrad King2010-06-101-1/+1
|/ / | | | | | | | | | | Even though this test is checking that the ctest running it can handle test output without newlines we should run the just-built CMake binary. This allows the MemCheck test mode to check the correct CMake.
* | Merge branch 'per-config-link-flags'Brad King2010-06-075-0/+69
|\ \
| * | Intel-specific workaround for LinkFlags testsBrad King2010-06-033-2/+13
| | | | | | | | | | | | | | | | | | | | | | | | The Intel C compiler for Linux does not seem to reject any bad flags or object files on its link lines. Work around the problem by using a preprocessor #error directive to ensure that BADFLAG appears in the build output. This does not really achieve the purpose of the tests but it allows them to pass.
| * | Borland-specific bad flag for LinkFlags testsBrad King2010-06-021-6/+9
| | | | | | | | | | | | | | | | | | The Borland librarian actually creates a BADFLAG.obj when the object is missing the first time! This causes later tests to not reject it. Instead use a Borland-specific variation on the flag.
| * | Better "bad" flag in LinkFlags testBrad King2010-06-011-6/+7
| | | | | | | | | | | | | | | The Intel C Compiler for Linux ignores _BADFLAG_ when linking! Use a flag that looks like a missing object file to ensure its rejection.
| * | Add STATIC_LIBRARY_FLAGS_<CONFIG> property (#10768)Brad King2010-05-281-3/+0
| | | | | | | | | | | | This is a per-configuration version of STATIC_LIBRARY_FLAGS.
| * | Test LINK_FLAGS and STATIC_LIBRARY_FLAGS (#10768)Brad King2010-05-284-0/+57
| |/ | | | | | | | | | | Add a LinkFlags test series to check that these properties work. Since no link flag is accepted everywhere we test for presence of flags by adding a bad flag and looking for the complaint in the test output.
* | Merge branch 'fix-large-output-test'Brad King2010-06-072-0/+6
|\ \
| * | Use the long test timeout value for SubmitLargeOutput.David Cole2010-06-032-0/+6
| |/ | | | | | | | | | | Hopefully this will be a large enough value to get the large output test to pass on the still exceedingly slow dash19.
* | Merge branch 'update_release_scripts'Brad King2010-06-071-1/+1
|\ \
| * | change nightly release builds to use next, and move qmake on dash2win64Bill Hoffman2010-05-281-1/+1
| |/
* | Merge branch 'add-git-to-CheckSourceTreeTest'Brad King2010-06-072-53/+176
|\ \
| * | Allow return value of 1 from git status.David Cole2010-05-281-3/+3
| | |
| * | Further refinements to the CheckSourceTree test.David Cole2010-05-271-4/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | Echo results of calling git status before exiting with an error. Add one special case so that the test may pass on the dashmacmini2 continuous dashboard, despite a 'git status' non-zero return code. More logic like this may be required. I will re-evaluate based on tomorrow's nightly dashboard runs.
| * | Add git support to the CMake.CheckSourceTree test.David Cole2010-05-272-53/+153
| |/ | | | | | | | | | | | | | | | | | | Additionally, output some more information in both cvs and git cases. When it is a cvs checkout, echo the contents of CVS/Root and CVS/Repository to the test output. When it is a git checkout, echo the output of 'git branch -a'. This will allow us to see more details about any given CMake source tree right in the CDash results for this test.
* | Merge branch 'improve-file-download'Brad King2010-06-074-0/+54
|\ \ | | | | | | | | | | | | Conflicts: Modules/ExternalProject.cmake
| * | Improve FILE(DOWNLOAD) and ExternalProject.David Cole2010-05-274-0/+54
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improve FILE(DOWNLOAD ...): - Add percent complete progress output to the FILE DOWNLOAD command. This progress output is off by default to preserve existing behavior. To turn it on, pass SHOW_PROGRESS as an argument. - Add EXPECTED_MD5 argument. Verify that the downloaded file has the expected md5 sum after download is complete. - Add documentation for SHOW_PROGRESS and EXPECTED_MD5. When the destination file exists already and has the expected md5 sum, then do not bother re-downloading the file. ("Short circuit" return.) Also, add a test that checks for the status output indicating that the short circuit behavior is actually occurring. Use a binary file for the test so that the md5 sum is guaranteed to be the same on all platforms regardless of "shifting text file line ending" issues. Improve ExternalProject: - Add argument URL_MD5. - Add verify step that compares md5 sum of .tar.gz file before extracting it. - Add md5 check to download step, too, to prevent unnecessary downloads. - Emit a warning message when a file is not verified. Indicate that the file may be corrupt or that no checksum was specified.
* | Merge branch 'add-git-to-ExternalProject'Brad King2010-06-072-4/+84
|\ \ | | | | | | | | | | | | Conflicts: Modules/ExternalProject.cmake
generated by cgit v0.12 at 2024-10-31 15:50:14 (GMT)