summaryrefslogtreecommitdiff
path: root/.gitlab-ci/deqp-runner.sh
diff options
context:
space:
mode:
authorJuan A. Suarez Romero <jasuarez@igalia.com>2021-01-26 19:13:21 +0100
committerMarge Bot <eric+marge@anholt.net>2021-02-15 15:47:31 +0000
commit5d0c96a8c2c5410b330e5389aab43227fafc1b1f (patch)
tree2dde9ad2c9088c57a05017c6e648a23ed1f53872 /.gitlab-ci/deqp-runner.sh
parent3d4c13f3b8e40c3ae1825bcb695bffe49d2ffb70 (diff)
downloadmesa-5d0c96a8c2c5410b330e5389aab43227fafc1b1f.tar.gz
ci: add option to overwrite CPU arch
When loading Vulkan ICD file, it uses the CPU machine identifier to load the correct one, in case multiple versions are installed. This is fine if the machine where Mesa has been built and the machine where the test is run are exactly the same. But this is not always the case. As example, for armhf architecture, the machine where Mesa is built is identified as `arm7hlf`, but the Raspberry Pi 4 is identified as `armv7l`, so it will fail to load the ICD file, though both are totally compatible. This allow to define the architecture instead. Signed-off-by: Juan A. Suarez Romero <jasuarez@igalia.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8745>
Diffstat (limited to '.gitlab-ci/deqp-runner.sh')
-rwxr-xr-x.gitlab-ci/deqp-runner.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/.gitlab-ci/deqp-runner.sh b/.gitlab-ci/deqp-runner.sh
index 92f97045fe5..8a52b7909cc 100755
--- a/.gitlab-ci/deqp-runner.sh
+++ b/.gitlab-ci/deqp-runner.sh
@@ -34,7 +34,7 @@ INSTALL=`pwd`/install
# Set up the driver environment.
export LD_LIBRARY_PATH=`pwd`/install/lib/
export EGL_PLATFORM=surfaceless
-export VK_ICD_FILENAMES=`pwd`/install/share/vulkan/icd.d/"$VK_DRIVER"_icd.`uname -m`.json
+export VK_ICD_FILENAMES=`pwd`/install/share/vulkan/icd.d/"$VK_DRIVER"_icd.${VK_CPU:-`uname -m`}.json
# the runner was failing to look for libkms in /usr/local/lib for some reason
# I never figured out.