[CI] Temporarily disable tests requiring spirv-tools in CI

[uditagarwal97]

#16724 installed spirv-tools on Linux docker containers and now some llvm-spirv tests are failing due to this (example: https://github.com/intel/llvm/actions/runs/12915358763/job/36017038536).
In this PR, we disable detection of spirv-tools LIT feature temporarily in CI to fix post-commit.

[AlexeySachkov]

Approving to unblock fixing CI failures, but llvm-spirv changes should either be upstreamed, or tracked in #7592 to remind us to revert them

[maarquitos14]

I'm okay with merging this to fix post-commit.

About the root cause, the problem seems to be that the path for all spirv-tools binaries is not found:

llvm-lit: /__w/llvm/llvm/src/llvm/utils/lit/lit/llvm/subst.py:126: note: Did not find spirv-as in SPIRV_AS_PATH-NOTFOUND
llvm-lit: /__w/llvm/llvm/src/llvm/utils/lit/lit/llvm/subst.py:126: note: Did not find spirv-dis in SPIRV_AS_PATH-NOTFOUND
llvm-lit: /__w/llvm/llvm/src/llvm/utils/lit/lit/llvm/subst.py:[12](https://github.com/intel/llvm/actions/runs/12918158681/job/36026109985#step:14:13)6: note: Did not find spirv-link in SPIRV_AS_PATH-NOTFOUND
llvm-lit: /__w/llvm/llvm/src/llvm/utils/lit/lit/llvm/subst.py:126: note: Did not find spirv-val in SPIRV_AS_PATH-NOTFOUND

I'm not sure why, I cannot reproduce locally. If you help me reproduce the issue, I can try and fix it.

[uditagarwal97]

@intel/llvm-gatekeepers I think we are good to merge this.

[uditagarwal97]

Hi @maarquitos14, @intel/dpcpp-spirv-reviewers,
I think I know what caused postcommit failures after installing spirv-tools on CI:

So, in llvm-spirv, we detect spirv-tools using two methods: using pkg-config (main) or cmake (fallback)(https://github.com/intel/llvm/blob/sycl/llvm-spirv/CMakeLists.txt#L123)

1. Using pkg-config:
   Our CI Linux container does not have pkg-config installed, unlike internally or in Podman's Ubuntu24 image.
   So, if I just install pkg-config in the docker container, we are able to correctly find spirv-tools and llvm-spirv LIT tests passes correctly.

2. Using cmake:
   Since we did not have pkg-config installed, llvm-spirv was using cmake to find spirv-tools. However, I think there's a bug in spiv-tools's official Ubuntu 24 installation package that we obtained via:

. /etc/os-release
curl -L "https://packages.lunarg.com/lunarg-signing-key-pub.asc" | apt-key add -
echo "deb https://packages.lunarg.com/vulkan $VERSION_CODENAME main" | tee -a /etc/apt/sources.list
apt update && apt install -yqq spirv-tools

The installation package does not have the correct CMake target import file. Here's the import files apt install spirv-tools installed:

$:/usr/lib/x86_64-linux-gnu/cmake/SPIRV-Tools-tools# ls
SPIRV-Tools-toolsConfig.cmake   SPIRV-Tools-toolsTargets.cmake  SPIRV-Tools-toolsTargets-none.cmake

Notice the SPIRV-Tools-toolsTargets-none.cmake file - the none here refers to the build config. So, if we do get_target_property(SPIRV_AS_PATH spirv-as IMPORTED_LOCATION_RELEASE) or get_target_property(SPIRV_AS_PATH spirv-as IMPORTED_LOCATION_DEBUG) (that we use to get spirv-as path: https://github.com/intel/llvm/blob/sycl/llvm-spirv/test/CMakeLists.txt#L56), it will not load this file because none is an invalid build config for LLVM project. If I rename this file, SPIRV-Tools-toolsTargets-none.cmake --> SPIRV-Tools-toolsTargets-debug.cmake and manually replace NONE to DEBUG in build config, cmake correctly loads the file and all llvm-spriv LIT tests correct passes. Btw, if we build spirv-tools locally, it produces the SPIRV-Tools-toolsTargets-debug.cmake or SPIRV-Tools-toolsTargets-release.cmake file, depending on build config.
So, that's why I think there's a bug in spiv-tools official installation package.

Solution:
For the time being, I think we can just install pkg-config in the CI container - we also use pkg-config internally, plus, it will take some time to confirm and get the cmake bug fixed, which, at best, will happen in the next spirv-tools release.

PS:- I've installed spirv-tools on Windows CI machines and it is working fine: https://github.com/intel/llvm/actions/runs/12934269927/job/36192622174#step:14:1

[maarquitos14]

@uditagarwal97 Thanks for the thorough investigation! I'm good with the suggested solution, let me know if you need any help.