1. 24 May, 2019 1 commit
    • Zsolt Parragi's avatar
      Tests: fix failures with gnu mode clang on windows · 4819ff96
      Zsolt Parragi authored
          Root causes were:
          * Using incorrect conditions (assuming MSVC-like command line mode)
          * Trying to compile the MSVC STL in C++11 mode, when parts of it require
            C++14 or enabling MS extensions in clang.
          * Missing flush in a testcase using stdout in a dll and a main part
          with static crt
      4819ff96
  2. 22 May, 2019 1 commit
  3. 13 Aug, 2012 2 commits
    • Kitware Robot's avatar
      Remove CMake-language block-end command arguments · 9db31162
      Kitware Robot authored
      Ancient versions of CMake required else(), endif(), and similar block
      termination commands to have arguments matching the command starting the
      block.  This is no longer the preferred style.
      
      Run the following shell code:
      
      for c in else endif endforeach endfunction endmacro endwhile; do
          echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      egrep -z -v 'Tests/CMakeTests/While-Endwhile-' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
      9db31162
    • Kitware Robot's avatar
      Convert CMake-language commands to lower case · 77543bde
      Kitware Robot authored
      Ancient CMake versions required upper-case commands.  Later command
      names became case-insensitive.  Now the preferred style is lower-case.
      
      Run the following shell code:
      
      cmake --help-command-list |
      grep -v "cmake version" |
      while read c; do
          echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g'
      done >convert.sed &&
      git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' |
      egrep -z -v '^(Utilities/cm|Source/kwsys/)' |
      xargs -0 sed -i -f convert.sed &&
      rm convert.sed
      77543bde
  4. 28 Jan, 2010 1 commit
  5. 10 Dec, 2009 1 commit
    • Brad King's avatar
      Always use a configuration for CMake tests · faf6d82b
      Brad King authored
      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.
      faf6d82b
  6. 01 Dec, 2009 1 commit
    • Brad King's avatar
      Always use a configuration for CTestTestTimeout · 7380d3ab
      Brad King authored
      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.
      7380d3ab
  7. 24 Nov, 2009 1 commit
    • Brad King's avatar
      Improve fake $HOME test isolation code · 1d6e7ed7
      Brad King authored
      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.
      1d6e7ed7
  8. 23 Nov, 2009 1 commit
    • Brad King's avatar
      Fake $HOME to isolate tests from user · 647d7105
      Brad King authored
      On platforms with $HOME in the environment, some of our features use it
      to store information in the user home directory.  However, tests for
      these features should not touch the real user home directory.  Instead
      we configure a fake $HOME that points inside the build tree for use
      during testing.
      
      See issue #9949.
      647d7105
  9. 05 Jan, 2009 1 commit