From 8749c25beb87c62f29f16dd42a24ee14e1595012 Mon Sep 17 00:00:00 2001 From: Mogball Date: Thu, 14 Nov 2024 12:20:41 -0800 Subject: [PATCH] Fix `gtest_discover_tests` timeout argument `gtest_discover_tests` runs the built unittest executable to create a distinct CMake target for every individual unittest in each executable. However, this was previously noted to time out on MacOS frequently (because MacOS scans newly built executables for viruses, or something...) but the timeout argument was incorrectly specified. --- cmake/AddTritonUnitTest.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmake/AddTritonUnitTest.cmake b/cmake/AddTritonUnitTest.cmake index 24fb20a72b8c..2eda7df3723e 100644 --- a/cmake/AddTritonUnitTest.cmake +++ b/cmake/AddTritonUnitTest.cmake @@ -35,5 +35,5 @@ function(add_triton_ut) # Without the TEST_DISCOVERY_TIMEOUT, the tests randomly time out on my mac # laptop. I think the issue may be that the very first time you run a program # it's a bit slow. - gtest_discover_tests(${__NAME} PROPERTIES TEST_DISCOVERY_TIMEOUT 60) + gtest_discover_tests(${__NAME} DISCOVERY_TIMEOUT 60) endfunction()