Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | GoogleTest: Add missing test case for gtest_discover_tests failure | Ryan Thornton | 2020-03-11 | 1 | -1/+0 |
| | | | | | | | | | | | | | | Discovery timeout test needs split out into two components: - build - test Building the project should result in a failure due to the timeout when executing gtest discovery as a post build step. Likewise, if you ran CTest after this build failure, we should *also* detect that the discovery_timeout_test has not been built because no discovery_timeout_test[1]_tests.cmake has been created due to the test discovery failure (caused by the timeout). | ||||
* | GoogleTest: Rename TIMEOUT parameter to avoid clash | Craig Scott | 2018-03-15 | 1 | -0/+1 |
In gtest_discover_tests(), the TIMEOUT keyword was making it impossible to set the TIMEOUT test property via the PROPERTIES keyword. This would be a frequent case, but it doesn't complain and instead silently does something different to what would normally be expected. The TIMEOUT keyword has been renamed to DISCOVERY_TIMEOUT, thereby removing the clash. This is a breaking change. 3.10.1 and 3.10.2 were the only versions that supported the TIMEOUT keyword and uses of it were likely not working as intended. Fixes: #17801 |