diff options
| author | Brad King <brad.king@kitware.com> | 2020-06-01 17:36:13 (GMT) |
|---|---|---|
| committer | Brad King <brad.king@kitware.com> | 2020-06-01 17:42:16 (GMT) |
| commit | 37bf7eb7a6440d7b2465a5e69fbf820217ac7eb3 (patch) | |
| tree | 14a119a02da479b9c0479f4b9cee558d847918a2 /Tests/PythonCoverage/coveragetest/test_foo.py | |
| parent | 1d2c8ae209e4cc0121310b0da10063b68f43bc68 (diff) | |
| download | CMake-37bf7eb7a6440d7b2465a5e69fbf820217ac7eb3.zip CMake-37bf7eb7a6440d7b2465a5e69fbf820217ac7eb3.tar.gz CMake-37bf7eb7a6440d7b2465a5e69fbf820217ac7eb3.tar.bz2 | |
Tests: Skip RunCMake.try_compile RerunCMake-nowork case on 1s filesystems
On low-resolution filesystems, `Makefile` can end up with the same
time stamp as `CMakeCache.txt`. CMake must re-run in this case to
be conservative, but that invalidates the `-nowork` cases.
Rather than trying to detect 1s filesystems, just add an option
called `CMake_TEST_FILESYSTEM_1S` that external scripts can use
to tell CMake's test suite about this.
Diffstat (limited to 'Tests/PythonCoverage/coveragetest/test_foo.py')
0 files changed, 0 insertions, 0 deletions