From f5e79004e28195f51cba4baff01615f6ce29b5bf Mon Sep 17 00:00:00 2001 From: Brad King Date: Wed, 6 Apr 2016 13:40:10 -0400 Subject: [PATCH] Tests: Work around filesystem timestamp bugs in RunCMake.BuildDepends The Custom-Symbolic-and-Byproduct case fails strangely on some filesystems used by our nightly testing. Somehow on the first build the `use-byproduct` output ends up with a timestamp older than `gen-byproduct-stamp` even though the build log clearly shows them build in the correct order (and must according to build system dependencies). Work around this problem by adding an extra delay before building `use-byproduct`. Tested-by: Gerhard Grimm --- Tests/RunCMake/BuildDepends/Custom-Symbolic-and-Byproduct.cmake | 1 + 1 file changed, 1 insertion(+) diff --git a/Tests/RunCMake/BuildDepends/Custom-Symbolic-and-Byproduct.cmake b/Tests/RunCMake/BuildDepends/Custom-Symbolic-and-Byproduct.cmake index 6948c35bf..687c8271f 100644 --- a/Tests/RunCMake/BuildDepends/Custom-Symbolic-and-Byproduct.cmake +++ b/Tests/RunCMake/BuildDepends/Custom-Symbolic-and-Byproduct.cmake @@ -10,6 +10,7 @@ add_custom_target(produce DEPENDS gen-byproduct) add_custom_command( OUTPUT use-byproduct DEPENDS ${CMAKE_CURRENT_BINARY_DIR}/byproduct + COMMAND ${CMAKE_COMMAND} -E sleep 1.125 # workaround buggy filesystem timestamps COMMAND ${CMAKE_COMMAND} -E touch use-byproduct ) add_custom_target(drive ALL DEPENDS use-byproduct)