1. 11 Sep, 2018 2 commits
  2. 10 Sep, 2018 6 commits
    • Brad King's avatar
      Merge branch 'FindMPI-restore-flags-string' into release-3.12 · e0e56abe
      Brad King authored
      Merge-request: !2368
    • Brad King's avatar
      Merge branch 'fix-ctest_start-track' into release-3.12 · 3eda5cdd
      Brad King authored
      Merge-request: !2366
    • Brad King's avatar
      FindMPI: Restore MPI_<LANG>_COMPILE_FLAGS as a command-line string · e374b9f1
      Brad King authored
      Refactoring in commit v3.10.0-rc1~103^2~2 (FindMPI: Modernization from
      ground up, 2017-04-25) accidentally left this variable set as a copy of
      the `;`-list in `MPI_<LANG>_COMPILE_OPTIONS`, but the flags variable is
      documented as a command-line string.  Restore it now.
      Fixes: #18349
    • Kyle Edwards's avatar
      CTest: Fix regression in ctest_start() · 09f0325e
      Kyle Edwards authored
      The format for the TAG file was changed in 3.12, and the way it was
      read caused a regression which changed how the track was decided. This
      commit fixes the regression.
      Fixes #18347.
    • Brad King's avatar
      Merge branch 'ctest-fix-test-load' into release-3.12 · 68f2b471
      Brad King authored
      Merge-request: !2362
    • Brad King's avatar
      CTest: Fix --test-load regression · 292ec157
      Brad King authored
      The `ctest --test-load` option is implemented in `StartNextTests` by not
      starting any tests when the load is too high and instead sleeping and
      then returning.  Prior to commit v3.11.0-rc1~117^2 (CTest: Re-implement
      test process handling using libuv, 2017-12-10) our outer loop in
      `RunTests` would immediately call `StartNextTests` again.  However, now
      the `uv_run` loop may simply terminate if there are no tests running
      because no events are left pending.
      Fix this by converting the sleep in `StartNextTests` into a libuv timer
      that it starts instead.  This avoids leaving `uv_run` with no pending
      events.  In the case that there are other running tests this also allows
      CTest to detect when they finish even if it during the wait period where
      we previously slept.
      This regression was not caught by the test suite because it only
      verified that we do not start new tests when the load was too high and
      not that we proceed to start tests when the load drops.  Revise the test
      suite to cover both.
      Fixes: #18338
  3. 07 Sep, 2018 1 commit
  4. 05 Sep, 2018 4 commits
  5. 04 Sep, 2018 2 commits
  6. 30 Aug, 2018 3 commits
  7. 28 Aug, 2018 2 commits
    • Brad King's avatar
      Merge branch 'android-ndk-r18' into release-3.12 · 0e764082
      Brad King authored
      Merge-request: !2319
    • Brad King's avatar
      Android: Add support for NDK r18 · ca97d4cb
      Brad King authored
      NDK r18 drops GCC toolchains and some STL types.  We need to choose a
      clang toolchain by default when no gcc toolchains are available.  Switch
      the STL type default to `c++_static` when the old `gnustl_static`
      default is not available.
      Update the test suite to not run tests for STL types that do not exist.
      Also do not expect the gcc toolchain `cpp` tool to be available because
      r18 does not provide it.  Also teach it to tolerate `gcc -dumpmachine`
      output like `arm--linux-android` that differs from the toolchain prefix.
      Fixes: #18301
  8. 24 Aug, 2018 2 commits
  9. 23 Aug, 2018 5 commits
  10. 17 Aug, 2018 1 commit
  11. 16 Aug, 2018 2 commits
  12. 09 Aug, 2018 2 commits
  13. 01 Aug, 2018 2 commits
  14. 31 Jul, 2018 2 commits
  15. 29 Jul, 2018 1 commit
  16. 27 Jul, 2018 1 commit
    • Brad King's avatar
      CPack: Restore support for 0-valued version components · ed015bde
      Brad King authored
      In commit v3.12.0-rc1~136^2 (CPack: Use project version as default for
      `CPACK_PACKAGE_VERSION`, 2018-04-29) we did not account for the value of
      `CMAKE_PROJECT_VERSION_{MAJOR,MINOR,PATCH}` having `0`.  Fix the logic
      to distinguish between unprovided version components and `0` components.
      While at it, add a test case covering the behavior described in the
      documentation by the original commit.  The number of version components
      in the package name should match those provided to the `project()`
      command `VERSION` option.
      Fixes: #18199
  17. 25 Jul, 2018 2 commits