summaryrefslogtreecommitdiffstats
path: root/Tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'version'Brad King2010-05-171-1/+2
|\
| * Report commit hash in CMake development versionsBrad King2010-04-231-1/+2
| | | | | | | | | | | | For builds from Git repositories, add "-g<commit>" to the end of the version number. If the source tree is modified, append "-dirty". For builds from CVS checkouts, add "-cvs-<branch>".
* | Disable purify on unix, as it works differently and ctest can't use it.Bill Hoffman2010-05-112-0/+16
| |
* | Fix CTestTestScheduler sporadic failure.Zach Mullen2010-05-073-5/+5
| | | | | | | | Increased the time difference between each test so that overburdened systems won't fail this test sometimes.
* | CTest: Submit author email in Update.xmlBrad King2010-05-071-0/+7
| | | | | | | | | | | | | | Add the <Email>...</Email> element in Update.xml for each commit reported. This field was defined by Dart but never really used. Distributed version control systems use author name and email instead of a user id, so now it makes sense to use this field.
* | Fix 'Architecture' test for more Mac linkersBrad King2010-05-061-1/+1
| | | | | | | | | | | | | | | | | | Some Mac linkers produce the message "file was built for unsupported file format which is not the architecture being linked" for this test. Update the test output regex to match it.
* | Teach ctest_update about Git submodulesBrad King2010-05-042-2/+71
| | | | | | | | | | | | | | | | | | | | | | Git does not automatically checkout the matching version of a submodule when it checks out a new version of the parent project in the work tree. If the submodule reference changed in the parent project then we were reporting the submodule path as a local modification. Work around the problem in ctest_update using "git submodule update" after "git pull". For projects with no submodules this is a no-op. See issue #10662. Also add a submodule to the test project for CTest.UpdateGIT to test the work-around.
* | Fix missing set of MSVC10 and add CheckCompilerRelatedVariables test.David Cole2010-04-302-0/+87
|/
* Fix for StopTime for cases when gmtime is a day ahead of localtimeZach Mullen2010-03-181-2/+2
|
* More debugging of StopTime testZach Mullen2010-03-182-3/+16
|
* Output times during StopTime test for debuggingZach Mullen2010-03-171-0/+4
|
* Move get_date call closer to ctest_test for more predictable results.Zach Mullen2010-03-171-3/+4
|
* Add the --stop-time argumentZach Mullen2010-03-176-1/+304
| | | | Unit test and script hook for STOP_TIME
* Add CMAKE_TESTS_CDASH_SERVER variable and CTestSubmitLargeOutput test.David Cole2010-03-087-4/+128
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If defined and non-empty, the value of CMAKE_TESTS_CDASH_SERVER should point to a CDash server willing to accept submissions for a project named PublicDashboard. On machines that also run a CDash dashboard, set this variable to "http://localhost/CDash-trunk-Testing" so that the CMake tests that submit dashboards do not have to send those submissions over the wire. The CTestSubmitLargeOutput test runs a dashboard that has a test that produces very large amount of output on stdout/stderr. Since we do not even want to attempt to send such large output over the wire, this test is off by default unless the CMAKE_TESTS_CDASH_SERVER server is localhost. This test is expected to cause a submission failure when sent to CDash. It passes if the submit results contain error output. It fails if the submit succeeds. CMAKE_TESTS_CDASH_SERVER: CDash server used by CMake/Tests. If not defined or "", this variable defaults to the server at http://www.cdash.org/CDash. If set explicitly to "NOTFOUND", curl tests and ctest tests that use the network are skipped. If set to something starting with "http://localhost/", the CDash is expected to be an instance of CDash used for CDash testing, pointing to a cdash4simpletest database. In these cases, the CDash dashboards should be run first.
* Remove empty_binary_dir command in new unit testZach Mullen2010-03-032-3/+1
|
* Add unit test for RESOURCE_LOCK test propertyZach Mullen2010-03-035-1/+85
|
* Different versions of cygwin report differet messages for cygwinBill Hoffman2010-02-261-2/+2
| | | | | For cygwin pass the badexe test if either ***Failed or BAD_COMMAND show up in the output of the test.
* Change the tag to be master from CVS for release scriptsBill Hoffman2010-02-251-2/+2
|
* Fix problem with ExternalProject test in in-source builds.David Cole2010-02-171-0/+11
|
* Add a high COST value to BootstrapTest so that it will be scheduled first in ↵Zach Mullen2010-02-111-0/+2
| | | | parallel ctest executions.
* Make CTest.UpdateCVS robust to some cvs clientsBrad King2010-02-102-2/+3
| | | | | | | | | | | | | | Commit "Teach CTest.Update tests to strongly check entries" (2010-02-09) started checking Update.xml entries strongly. This revealed that some cvs clients report "U CTestConfig.cmake" during update even though the file did not change and it selects the same revision. As a result the test fails with Update.xml has extra unexpected entries: Updated{CTestConfig.cmake} We fix the test to tolerate this particular extra entry without failing.
* Fix configure time error that occurs when there is a backslash in the HOME ↵David Cole2010-02-101-1/+2
| | | | environment variable.
* Teach CTest.UpdateGIT test to fake file timestampBrad King2010-02-092-0/+12
| | | | | | | We wrap the git executable in a shell script that touches one source file after 'git pull'. This makes the file newer than the index even though it has not actually changed. If CTest does not refresh the index properly then the test will fail with a bogus modified file.
* Teach CTest.Update tests to strongly check entriesBrad King2010-02-091-19/+47
| | | | | | Previously these tests just checked for matching file names in the Update.xml files. Now we check the update types (Updated, Modified, or Conflicting) and reject unexpected extra entries.
* Re-enabled Scheduler test and fixed the underlying problem.Zach Mullen2010-02-031-10/+10
|
* Disable Scheduler test until underlying problem is resolved.Zach Mullen2010-02-031-10/+10
|
* Add unit test to ensure that CTestCostData scheduling works correctlyZach Mullen2010-02-035-0/+79
|
* Add alternate per-vendor compiler id detectionBrad King2010-02-012-0/+32
| | | | | | | At least one Fortran compiler does not provide a preprocessor symbol to identify itself. Instead we try running unknown compilers with version query flags known for each vendor and look for known output. Future commits will add vendor-specific flags/output table entries.
* Avoid PathScale cmd-line bug in TryCompile testBrad King2010-01-251-2/+8
| | | | | | | | | | | | | | | | | | | | The PathScale compiler silently accepts unknown options that start in more than one '-': $ touch foo.c $ pathcc -c foo.c --junk $ echo $? 0 $ pathcc -c foo.c ---junk $ echo $? 0 $ pathcc -c foo.c -junk pathcc ERROR parsing -junk: unknown flag $ echo $? 2 We teach the TryCompile to pass a bogus flag with only one '-' instead of three '-'s for this compiler.
* Skip Fortran module mangling test on PathScaleBrad King2010-01-251-1/+1
| | | | | | We disable this test because PathScale Fortran mangles module symbols as "MYSUB.in.MYMODULE" so we cannot interface with it from C. We already did this for SunPro and MIPSpro.
* Fix escapes in Fortran depend.make entriesBrad King2010-01-042-4/+11
| | | | | | | Makefile dependencies must be escaped using cmLocalGenerator::Convert with the cmLocalGenerator::MAKEFILE option. This fixes Fortran module dependencies with spaces in the path. We test the fix by adding a space to one of the module paths in the Fortran test.
* Fix issue #10060 - add APPEND arg to ctest_start command.David Cole2009-12-291-0/+4
| | | | If APPEND is given to ctest_start, it will read the tag from the current existing Testing/TAG file rather than creating a new one based on the current time stamp. This allows a developer to run several dashboard scripts in a row, all of which will share the same tag/stamp/buildid when they finally get submitted to CDash. Now you can split the running of build phases and test phases for the same dashboard row into multiple scripts.
* Longer CTestTestTimeout default time on CygwinBrad King2009-12-211-1/+5
| | | | | | | | | The commit "Make CTestTestTimeout time configurable" added a CMake cache variable CTestTestTimeout_TIME to configure the length of the timeout used by the inner CTestTestTimeout test. The reason was to allow users on slow machines to give this test some extra time without extending the timeout for everyone. However, Cygwin CMake seems to load slowly enough that it is worth a longer default timeout for that platform.
* Test for SVNPath element in Update.xmlBrad King2009-12-182-3/+4
| | | | | | | The commit "Submit Subversion directory path in Update.xml" added the element <SVNPath>...</SVNPath> to Update.xml for Subversion work trees. This commit teaches the CTest.UpdateSVN test to verify the presence of the element.
* Fix BadExe test on cygwin.Bill Hoffman2009-12-181-6/+8
|
* Submit global tree revision in Update.xmlBrad King2009-12-182-0/+20
| | | | | | | We teach CTest to report in a <Revision> element the revision of the source tree that was tested. This makes sense for all modern VCS tools because they version the whole tree. We simply omit this element for CVS because it only versions files. See issue #7541.
* Test the CheckTypeSize moduleBrad King2009-12-174-0/+181
| | | | | We create test "Module.CheckTypeSize" to verify that type sizes get detected correctly.
* Teach ADD_TEST_MACRO about test namespacesBrad King2009-12-171-4/+6
| | | | | | We teach ADD_TEST_MACRO to transform names of the form "Namespace.Name" to the directory "Namespace/Name" and the project name "Name". This will allow new tests to be better organized.
* Workaround for CTestTestBadExe on CygwinZach Mullen2009-12-171-2/+6
|
* Add a test to build the CSE project if the optional cache entry ↵David Cole2009-12-151-0/+13
| | | | CMAKE_TEST_PROJECT_CSE_DIR is set.
* Honor real language flags in FortranC.Flags testBrad King2009-12-153-6/+10
| | | | | | The test overrides the CMAKE_C_FLAGS and CMAKE_Fortran_FLAGS to test passing a specific flag to the compiler wrapper scripts. We fix it to honor any outside flags needed for the real compiler.
* FortranCInterface: Support '=' in language flagsBrad King2009-12-151-2/+2
| | | | | | | | The commit "FortranCInterface: Honor language flags in checks" taught the FortranCInterface module to pass C and Fortran flags into its detection and verification checks. We improve on the change to allow the '=' character in the language flags. This requires passing the cache entry type with the -D options.
* Add one more possible error message from curl for the failed submit tests.David Cole2009-12-151-0/+1
|
* Test FortranCInterface flag propagationBrad King2009-12-144-0/+81
| | | | | | We create test FortranC.Flags to try passing per-language flags from a project into its FortranCInterface detect/verify checks. We wrap the compilers with scripts that enforce presence of expected flags.
* New decision method to enable Fortran testsBrad King2009-12-102-14/+50
| | | | | | | | | | CMake does not enable Fortran for its own build, but it needs to find a Fortran compiler to know if it is possible to enable Fortran tests. Previously we searched for a hard-coded list of Fortran compilers which was duplicated from the CMakeDetermineFortranCompiler.cmake module. We now run CMake on a small test project that enables the Fortran language and reports the compiler it found. This represents a more realistic check of whether the Fortran tests will be able to find a compiler.
* Always use a configuration for CMake testsBrad King2009-12-101-15/+3
| | | | | | | | | | Previously our EnforceConfig script that loads at test-time would only enforce a non-empty CTEST_CONFIGURATION_TYPE for CMake 2.6.2 and lower. Now we simply always enforce use of a configuration, and select one of the configurations that was built if none is given. This is necessary to run tests like CMake.Install that need to know the configuration with which CMake was built.
* Test 'install' target of CMake itselfBrad King2009-12-102-0/+50
| | | | | | We create option CMake_TEST_INSTALL to enable a new CMake.Install test. It tests running the "make install" target to install CMake itself into a test directory. We enable the option by default for dashboard builds.
* Apply CMake test-time config to all testsBrad King2009-12-101-4/+0
| | | | | | We configure an EnforceConfig.cmake script to load at CTest time. Previously we loaded it from Tests/CTestTestfile.cmake, but now we load it from the top level so it applies to all tests.
* Create CMakeLibTests output dir for XcodeBrad King2009-12-091-0/+10
| | | | | | | | | Xcode 2.x forgets to create the target output directory before linking the individual architecture pieces of a universal binary for the target CMakeLibTests. Then it passes the directory to -L and -F options when linking the and warns that the directory does not exist. We work around the problem by using a pre-build rule on the target to create the output directory.
* Test XML encoding with UTF-8 character validationBrad King2009-12-082-0/+48
| | | | This creates a unit test for cmXMLSafe. See issue #10003.
generated by cgit v0.12 at 2024-11-15 17:56:23 (GMT)