ci: Enable testing radeonsi's libva using libva-util unit tests.
authorEmma Anholt <emma@anholt.net>
Fri, 8 Oct 2021 20:17:27 +0000 (13:17 -0700)
committerMarge Bot <emma+marge@anholt.net>
Thu, 28 Oct 2021 23:17:19 +0000 (23:17 +0000)
commit8fb850651c77c0513c04952362b82b0ad1eff953
treea5410274d3dd8d3dbbd5b39b96389aa487bfe103
parente6ae0e9b953616fed894e02b9b8c2a52f269b0be
ci: Enable testing radeonsi's libva using libva-util unit tests.

We've noticed issues with these tests when uprevving Mesa in Chrome OS.
This CI catches some existing failures, and some debug-build assertion
failures as well.

To do this, uprev deqp-runner for its new gtest-runner command.  This
runner is not as efficient as I would hope, due to some expensive code in
gtest.  I've reported the issue to gtest and it should be easily fixable,
but for now it at least means we get to use the same baseline/skip/flake
handling we have from deqp and piglit runners.

I also fixed build-libdrm for our rootfses to not throw away libdrm's
share directory, which was causing a bunch of test-time spam from radeon's
libdrm when trying to look up its marketing name tables (not that big of a
deal for deqp-runner, but really noisy for piglit and libva-utils which
make gallium screens approximatly per-test).

Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13419>
.gitlab-ci.yml
.gitlab-ci/common/generate-env.sh
.gitlab-ci/container/build-deqp-runner.sh
.gitlab-ci/container/build-va-tools.sh [new file with mode: 0644]
.gitlab-ci/container/create-rootfs.sh
.gitlab-ci/container/lava_build.sh
.gitlab-ci/gtest-runner.sh [new file with mode: 0644]
.gitlab-ci/prepare-artifacts.sh
.gitlab-ci/test-source-dep.yml
src/gallium/drivers/radeonsi/ci/gitlab-ci.yml
src/gallium/drivers/radeonsi/ci/radeonsi-stoney-fails.txt