summaryrefslogtreecommitdiffstats
path: root/Tests/FindPython/Python2Module
diff options
context:
space:
mode:
authorscivision <scivision@users.noreply.github.com>2023-11-01 15:47:34 (GMT)
committerscivision <scivision@users.noreply.github.com>2023-11-07 02:46:17 (GMT)
commit7b4983536a634a7888466088a52319d7efe7a5c3 (patch)
tree7e09cb9853c305fb9127c7497229a14ce9f319ae /Tests/FindPython/Python2Module
parent51d985da3e12f06ff9349970093d38d497ed3da0 (diff)
downloadCMake-7b4983536a634a7888466088a52319d7efe7a5c3.zip
CMake-7b4983536a634a7888466088a52319d7efe7a5c3.tar.gz
CMake-7b4983536a634a7888466088a52319d7efe7a5c3.tar.bz2
Help:test prop WILL_FAIL clarify and example
This makes the WILL_FAIL behavior explicit. Users could be confused because some other build systems treat equivalent test properties as allowing a failure, but still pass on a passing test, and may catch SIGABRT unlike CMake. We show an example of how to wrap a test so that sigabrt, segfault, etc. are also handled by WILL_FAIL.
Diffstat (limited to 'Tests/FindPython/Python2Module')
0 files changed, 0 insertions, 0 deletions