| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Increased the time difference between each test so that overburdened systems won't fail this test sometimes.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Unit test and script hook for STOP_TIME
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
For cygwin pass the badexe test if either ***Failed or BAD_COMMAND
show up in the output of the test.
|
| |
|
|
|
|
| |
parallel ctest executions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We create test "Module.CheckTypeSize" to verify that type sizes get
detected correctly.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
CMAKE_TEST_PROJECT_CSE_DIR is set.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We create a new CMakeLibTests driver executable in which to writes unit
tests for CMakeLib. Our first test is a smoke-test of cmXMLParser.
|
|
|
|
| |
Replaced with a pass regex.
|
|
|
|
| |
executable, because it previously caused the outer ctest process to fail.
|
|
|
|
| |
running -D dashboards from the command line and running ctest_configure, ctest_build and ctest_test commands in -S scripts. Also, allow a script to change it by setting the CTEST_CONFIGURATION_TYPE variable: allows for multiple configuration build/test cycles within one script. Add a new signature for the cmake command build_command that accepts CONFIGURATION as one argument. The original build_command signature is still there, but now marked as deprecated in the documentation. Of course... also add CTestConfig tests to verify that -C is honored for -D dashboards and -S scripts.
|
|
|
|
|
|
|
|
| |
This test requires that the dashboard script it drives be invoked with
"ctest -C <config> -S ...". We create a "CTestTest_CONFIG" variable to
hold a configuration selected at test time. We use the configuration
given to the outer CTest, if any, and then default to either Debug or
the CMAKE_BUILD_TYPE.
|
|
|
|
|
|
|
|
|
|
|
| |
We extend the CTestTestTimeout test to check that when a test times out
its children (grandchildren of ctest) are killed. Instead of running
the timeout executable directly, we run it through a cmake script that
redirects the timeout executable output to a file. A second test later
runs and verifies that the timeout executable was unable to complete and
write data to the log file. Only if the first inner test times out and
the second inner test passes (log is empty) does the CTestTestTimeout
test pass.
|
|
|
|
|
| |
The test_clean target is supposed to remove all test build directories.
We add the build directory for CMakeBuildTest because it was missing.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The commit "Fake $HOME to isolate tests from user" started setting $HOME
in the CTest script environment. On some platforms tests depend on some
local configuration in the home directory, such as the "cvs login" for
KWSys in CTestTest3.
In this commit we now construct a fake home dir during CMake config step
and populate it with a .cvspass file needed by the test. We also check
CTEST_NO_TEST_HOME to optionally disable the test home.
See issue #9949.
|
|
|
|
|
| |
We create a LinkDirectory test to check that the policy OLD and NEW
behaviors work as documented. See issue #9697.
|
| |
|
|
|
|
| |
at the Tests/CMakeLists.txt level.
|
|
|
|
| |
added test coverage for passing absolute paths to subdirs.
|
| |
|
| |
|
|
|
|
| |
be done in parallel.
|
|
|
|
| |
[Cc]ouldn't and [Cc]ould not.
|
| |
|
| |
|
| |
|
|
|
|
| |
build on dashmacmini2 might have enough time to complete successfully. Use CMAKE_LONG_TEST_TIMEOUT instead of a hard-coded number for the test TIMEOUT property so that a calling script may adjust it by setting a higher CTEST_TEST_TIMEOUT value.
|
|
|
|
| |
build on dashmacmini2 might have enough time to complete successfully. Allow for up to 3 hours. After measuring successful runs for a few weeks, perhaps we can use a lower value.
|
| |
|
|
|
|
|
|
|
| |
We test (ARCHIVE|LIBRARY|RUNTIME)_OUTPUT_DIRECTORY_<CONFIG> properties
by building COnly as a subdirectory and setting the properties to put
its files in specific locations. We build an executable that verifies
the targets actually appear where expected.
|
|
|
|
| |
during the CPackComponents test. The purpose of each is to increase coverage of cmake.cxx.
|
|
|
|
| |
cmake generated build tree. Theoretically, each generation run with exactly the same arguments should be identical to the previous generation... Practically, there are differences. This is a tool to help us measure those differences. For now, the test always succeeds. Eventually, we may add the code to make it fail when there are differences.
|
| |
|
| |
|
|
|
|
| |
fully defined yet, we just run it as is and don't care much about the result.
|