Closed pvelesko closed 1 month ago
@pjaaskel I couldn't find another way to do this. Tried using CTEST_PRE_TEST
but it didn't do anything.
Since check.py
uses ctest as well, there's no simple way of doing this. In either case, just toggling the option on or off and reconfiguring cmake is enough here - you don't have to actually recompile the tests.
Merging this now now, we can implement a method that doesn't require CMake reconfigure later.
I meant that we'd restrict the list of XPASS tests (which is currently restricted only by those cpu/gpu cl/lz toggles) by checking from clinfo if the target supports doubles, and/or have a flag in check.py that drops the tests that are known to fail with doubles.
XPASS tests (which is currently restricted only by those cpu/gpu cl/lz toggles
I'm sorry what is XPASS? And what toggles are you talking about?
In any case, how would we know if the test is using doubles without inspecting the SPIR-V? Inspecting the source of all the tests is not reasonable as there are thousands of tests and relying on a predefined list won't work as soon as new tests are added.
Sorry for being unclear - not enough coffee consumed yet. Toggles in check.py which limit the list of tests expected to pass. You could inspect SPIR-V as you do know and dump the test cases that are expected to fail? But yep - this is not important.
Toggles in check.py which limit the list of tests expected to pass.
I'll add this approach to my backlog. Thank you for the suggestion.
This would be better as a check.py option as it's possible to run the same build on different devices, some of them supporting FP64, some not.