CMake

ExternalProjectLocal

command_line: D:\a\nightly-builds\nightly-builds\build\bin\ctest.exe "--build-and-test" "D:/a/nightly-builds/nightly-builds/Tests/ExternalProjectLocal" "D:/a/nightly-builds/nightly-builds/build/Tests/ExternalProjectLocal" "--build-generator" "Ninja" "--build-makeprogram" "C:/ProgramData/chocolatey/bin/ninja.exe" "--build-project" "ExternalProjectLocalTest" "--build-exe-dir" "D:/a/nightly-builds/nightly-builds/build/Tests/ExternalProjectLocal" "--test-command" "D:/a/nightly-builds/nightly-builds/build/bin/ctest" "-V"

working_directory: "./Tests"

Processors: 1

Execution Time: 36.296

Completion Status: Completed

Environment: #CTEST_RESOURCE_GROUP_COUNT=

stdout:

Internal cmake changing into directory: D:/a/nightly-builds/nightly-builds/build/Tests/ExternalProjectLocal
======== CMake output     ======
CMake Warning (dev) at D:/a/nightly-builds/nightly-builds/Modules/ExternalProject/shared_internal_commands.cmake:1261 (message):
  The DOWNLOAD_EXTRACT_TIMESTAMP option was not given and policy CMP0135 is
  not set.  The policy's OLD behavior will be used.  When using a URL
  download, the timestamps of extracted files should preferably be that of
  the time of extraction, otherwise code that depends on the extracted
  contents might not be rebuilt if the URL changes.  The OLD behavior
  preserves the timestamps from the archive instead, but this is usually not
  what you want.  Update your project to the NEW behavior or specify the
  DOWNLOAD_EXTRACT_TIMESTAMP option with a value of true to avoid this
  robustness issue.
Call Stack (most recent call first):
  D:/a/nightly-builds/nightly-builds/Modules/ExternalProject.cmake:3080 (_ep_add_download_command)
  CMakeLists.tx...
[This part of the test output was removed since it exceeds the threshold of 1024 bytes.]
Status: passed
Loading...