mirrors/mesa
0
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2024-11-28 04:34:25 +08:00
Code Issues Packages Projects Releases Wiki Activity
0cccf00436
mesa/.gitlab-ci/lava/lava-gitlab-ci.yml

117 lines
3.6 KiB
YAML
Raw Normal View History

gitlab-ci: Run dEQP on devices with Panfrost Include Panfrost's gitlab.ci.yml file from Mesa's main .gitlab-ci.yml so we test on devices with Panfrost. This uses LAVA to schedule jobs in the devices and will be the base for testing Etnaviv, Lima, etc. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-18 22:03:36 +08:00
.lava-test:
gitlab-ci: Move LAVA-related files into top-level ci dir In preparation for testing drivers other than Panfrost in LAVA labs. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-18 22:43:30 +08:00
extends:
gitlab-ci: Use the common run policy for LAVA jobs as well again Having different policies could have some weird results, e.g. changes only touching documentation (where the intention is not to run the pipeline by default) would still create a pipeline with the LAVA jobs running by default. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Engestrom <eric.engestrom@intel.com>
2019-12-06 16:39:40 +08:00
- .ci-run-policy
ci: Do not mark container / pages jobs as interruptible If another MR was merged while these were still running for the main project, the result could be no updated images in the main project registry (forcing a rebuild of the new images in all forked projects) or an outdated Mesa website. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6011>
2020-07-21 22:13:37 +08:00
# Cancel job if a newer commit is pushed to the same branch
interruptible: true
gitlab-ci: Run piglit tests with llvmpipe One job for the quick_gl profile, one for the glslparser & quick_shader profiles (doing these together takes hardly any more time than quick_shader alone). v2: * Don't break lava tests v3: * Remove piglit test artifacts paths: * Exclude some quick_shader tests again: - Test whose result flips between pass/fail/skip - *@vs_in tests, as not the same one of these gets picked every time v4: * Do not list passing tests in .gitlab-ci/piglit/*.txt (Eric Anholt) * Include the test number summary in .gitlab-ci/piglit/*.txt * Completely disable generating any vs_in tests in the piglit build. * Remove some more unneded files from the piglit build tree. * Exclude quick_gl arb_gpu_shader5 tests; they were all skipped anyway, as llvmpipe doesn't support this extension yet, but occasionally they would spuriously fail instead. v5: * Set LD_LIBRARY_PATH, so we actually test the Mesa build from the pipeline... * Verify that wflinfo reports the expected Mesa version * Pass -noreset to Xvfb v6: * Don't use autoscale runners, run piglit with -j4 (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net>
2019-10-22 23:16:52 +08:00
variables:
GIT_STRATEGY: none # testing doesn't build anything from source
gitlab-ci: Run GLES3 tests in dEQP on Panfrost We are able to run only 1/5th of the tests in around the same time that dEQP-GLES2 takes, so do that for now while more DUTs are installed. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3876>
2019-12-18 23:11:33 +08:00
ENV_VARS: "DEQP_PARALLEL=6"
ci: Add JOB_ARTIFACTS_BASE variable Used for both LAVA (uploading results to MinIO because we don't yet have non-ephemeral NFS storage) and Piglit (for the Tracie dashboard). Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 23:29:39 +08:00
FIXED_ENV_VARS: "CI_PIPELINE_ID=${CI_PIPELINE_ID} CI_JOB_ID=${CI_JOB_ID} CI_PAGES_DOMAIN=${CI_PAGES_DOMAIN} CI_PROJECT_NAME=${CI_PROJECT_NAME} CI_PROJECT_DIR=${CI_PROJECT_DIR} CI_PROJECT_PATH=${CI_PROJECT_PATH} CI_PROJECT_ROOT_NAMESPACE=${CI_PROJECT_ROOT_NAMESPACE} CI_SERVER_URL=${CI_SERVER_URL} DRIVER_NAME=${DRIVER_NAME} FDO_UPSTREAM_REPO=${FDO_UPSTREAM_REPO} PIGLIT_NO_WINDOW=1 PIGLIT_REPLAY_UPLOAD_TO_MINIO=1 MINIO_HOST=${MINIO_HOST} LAVA_TEST_SCRIPT=${LAVA_TEST_SCRIPT} VK_DRIVER=${VK_DRIVER} FLAKES_CHANNEL=${FLAKES_CHANNEL} PIPELINE_ARTIFACTS_BASE=${PIPELINE_ARTIFACTS_BASE} JOB_ARTIFACTS_BASE=${JOB_ARTIFACTS_BASE}"
gitlab-ci: Run GLES3 tests in dEQP on Panfrost We are able to run only 1/5th of the tests in around the same time that dEQP-GLES2 takes, so do that for now while more DUTs are installed. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3876>
2019-12-18 23:11:33 +08:00
DEQP_VERSION: gles2
ci/lava: Clean up variable naming, document them Our variable names haven't aged very well. Rename them to make them more clear and straightforward, especially when we bring in a third rootfs element to download. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 21:53:57 +08:00
# proxy used to cache data locally
FDO_HTTP_CACHE_URI: "http://caching-proxy/cache/?uri="
# base system generated by the container build job, shared between many pipelines
BASE_SYSTEM_HOST_PREFIX: "${MINIO_HOST}/mesa-lava"
BASE_SYSTEM_MAINLINE_HOST_PATH: "${BASE_SYSTEM_HOST_PREFIX}/${FDO_UPSTREAM_REPO}/${DISTRIBUTION_TAG}/${ARCH}"
BASE_SYSTEM_FORK_HOST_PATH: "${BASE_SYSTEM_HOST_PREFIX}/${CI_PROJECT_PATH}/${DISTRIBUTION_TAG}/${ARCH}"
ci: Make PIPELINE_ARTIFACTS_BASE a common variable $minio/artifacts/$project/$pipeline/ is common between all our CI. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 23:24:48 +08:00
# per-job build artifacts
ci/lava: Clean up variable naming, document them Our variable names haven't aged very well. Rename them to make them more clear and straightforward, especially when we bring in a third rootfs element to download. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 21:53:57 +08:00
MESA_BUILD_PATH: "${PIPELINE_ARTIFACTS_BASE}/mesa-${ARCH}.tar.gz"
ci: Add JOB_ARTIFACTS_BASE variable Used for both LAVA (uploading results to MinIO because we don't yet have non-ephemeral NFS storage) and Piglit (for the Tracie dashboard). Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 23:29:39 +08:00
JOB_RESULTS_PATH: "${JOB_ARTIFACTS_BASE}/results.tar.gz"
panfrost/ci: Initial commit These files implement running almost all of deqp-gles2 on Chomebooks of the rk3399-gru-kevin type in Collabora's LAVA lab. The approach follows what is currently being used for virglrenderer, but scheduling the actual test jobs via LAVA. We start by building a container in Docker that contains a suitable rootfs and kernel for the DUT, deqp and all dependencies for building Mesa itself. The Mesa is built and the rootfs, deqp and Mesa are combined in a cpio ramdisk. A LAVA job is generated, submitted to LAVA and the results are processed by simply comparing them to the expectations that are stored in git. Any code that changes the expectations (hopefully tests are fixed) needs to also update the expectations file. The next step is adding support for other devices, possibly in other LAVA labs. In order to use this, the repository has to be configured to run the gitlab-ci.yaml file from the panfrost/ci dir, and a LAVA token needs to be setup. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
2019-04-30 00:33:22 +08:00
script:
ci/lava: Wrap submission in a shell script Just do what we're already doing but in a shell script, which will make it less tedious to expand out later. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 20:11:02 +08:00
- ./artifacts/lava/lava-submit.sh
panfrost/ci: Initial commit These files implement running almost all of deqp-gles2 on Chomebooks of the rk3399-gru-kevin type in Collabora's LAVA lab. The approach follows what is currently being used for virglrenderer, but scheduling the actual test jobs via LAVA. We start by building a container in Docker that contains a suitable rootfs and kernel for the DUT, deqp and all dependencies for building Mesa itself. The Mesa is built and the rootfs, deqp and Mesa are combined in a cpio ramdisk. A LAVA job is generated, submitted to LAVA and the results are processed by simply comparing them to the expectations that are stored in git. Any code that changes the expectations (hopefully tests are fixed) needs to also update the expectations file. The next step is adding support for other devices, possibly in other LAVA labs. In order to use this, the repository has to be configured to run the gitlab-ci.yaml file from the panfrost/ci dir, and a LAVA token needs to be setup. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
2019-04-30 00:33:22 +08:00
artifacts:
gitlab-ci: Always name artifacts archive after the job producing it This will help determine which artifacts generate how much traffic. v2: * Add "mesa_" prefix to make it obvious which project the artifacts are from. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4085> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4085>
2020-03-06 19:35:17 +08:00
name: "mesa_${CI_JOB_NAME}"
panfrost/ci: Initial commit These files implement running almost all of deqp-gles2 on Chomebooks of the rk3399-gru-kevin type in Collabora's LAVA lab. The approach follows what is currently being used for virglrenderer, but scheduling the actual test jobs via LAVA. We start by building a container in Docker that contains a suitable rootfs and kernel for the DUT, deqp and all dependencies for building Mesa itself. The Mesa is built and the rootfs, deqp and Mesa are combined in a cpio ramdisk. A LAVA job is generated, submitted to LAVA and the results are processed by simply comparing them to the expectations that are stored in git. Any code that changes the expectations (hopefully tests are fixed) needs to also update the expectations file. The next step is adding support for other devices, possibly in other LAVA labs. In order to use this, the repository has to be configured to run the gitlab-ci.yaml file from the panfrost/ci dir, and a LAVA token needs to be setup. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
2019-04-30 00:33:22 +08:00
when: always
paths:
ci/lava: Return the run's results/ artifacts from the DUTs. Finally LAVA users will be able to see deqp XMLs on failures from the job's artifacts browser. This replaces a couple of one-off minio uploads in the piglit runner. Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10297>
2021-04-17 05:18:07 +08:00
- results/
exclude:
- results/*.shader_cache
after_script:
ci/lava: Clean up variable naming, document them Our variable names haven't aged very well. Rename them to make them more clear and straightforward, especially when we bring in a third rootfs element to download. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 21:53:57 +08:00
- wget -q "https://${JOB_RESULTS_PATH}" -O- | tar -xz
panfrost: ci: Add support for running the tests on RK3288 Build artifacts for armhf and schedule them on a Veyron Chromebook with RK3288. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
2019-05-03 23:48:48 +08:00
gitlab-ci/lava: Test Lima driver with dEQP Run dEQP on boards with Mali 400 and 450 in Baylibre's lab. There's lots of skipped tests because of crashes and undetermined behavior. May be a good idea to run the tests with valgrind and fix any issues found. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Vasily Khoruzhick <anarsoul@gmail.com> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
2019-10-06 23:49:56 +08:00
.lava-test:armhf:
gitlab-ci: Organize images using new REPO_SUFFIX templates feature Two benefits: Most docker image related environment variables can now be defined in the jobs where they're used instead of globally. The DEBIAN_TAG values are propagated to other jobs via YAML anchors. Images on https://gitlab.freedesktop.org/mesa/mesa/container_registry are now organized in separate repositories with a suffix matching the name of the job which makes sure the image is there. Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-11-12 01:13:28 +08:00
variables:
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
ARCH: armhf
KERNEL_IMAGE_NAME: zImage
KERNEL_IMAGE_TYPE: "type:\ zimage"
BOOT_METHOD: u-boot
ci: Use a single template for LAVA jobs It's a pain to keep both templates in sync and there aren't really that many differences. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9950>
2021-02-01 18:42:43 +08:00
LAVA_TEST_SCRIPT: "/install/deqp-runner.sh"
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
extends:
ci/lava: Switch LAVA jobs to x86 runners So we don't need to provision aarch64 servers, which are these days rarer than x8_64. In the switch to the new runner tags, switch to one which contains the device type, so we can dimension the runner jobs taking into account the number of DUTs available. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11108>
2021-05-31 15:03:04 +08:00
- .use-arm_build # for same $MESA_ARTIFACTS_TAG as in kernel+rootfs_armhf
- .use-x86_build
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
- .lava-test
ci: Use a single kernel+rootfs for both baremetal and LAVA jobs Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-13 13:40:36 +08:00
- .use-kernel+rootfs-arm
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
needs:
gitlab-ci: More stable URL for kernel and ramdisk artifacts, for LAVA Place the kernel and ramdisk into a place in the file server so the URL will only change when the contents also change. Also put the Mesa build into a separate tarball so the ramdisk's contents don't change every build. With proper caching in place, all devices in the same farm need only to download the mesa tarball once, saving time. As we switch to MinIO for making kernels and rootfs available to LAVA devices, we can stop using Docker to distribute them. Instead, build when needed in separate jobs that push directly to MinIO, from where LAVA devices can download them. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5515>
2020-04-01 19:07:46 +08:00
- kernel+rootfs_armhf
ci/lava: Switch LAVA jobs to x86 runners So we don't need to provision aarch64 servers, which are these days rarer than x8_64. In the switch to the new runner tags, switch to one which contains the device type, so we can dimension the runner jobs taking into account the number of DUTs available. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11108>
2021-05-31 15:03:04 +08:00
- x86_build
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
- meson-armhf
panfrost: ci: Add support for running the tests on RK3288 Build artifacts for armhf and schedule them on a Veyron Chromebook with RK3288. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io>
2019-05-03 23:48:48 +08:00
gitlab-ci/lava: Test Lima driver with dEQP Run dEQP on boards with Mali 400 and 450 in Baylibre's lab. There's lots of skipped tests because of crashes and undetermined behavior. May be a good idea to run the tests with valgrind and fix any issues found. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Vasily Khoruzhick <anarsoul@gmail.com> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
2019-10-06 23:49:56 +08:00
.lava-test:arm64:
gitlab-ci: Organize images using new REPO_SUFFIX templates feature Two benefits: Most docker image related environment variables can now be defined in the jobs where they're used instead of globally. The DEBIAN_TAG values are propagated to other jobs via YAML anchors. Images on https://gitlab.freedesktop.org/mesa/mesa/container_registry are now organized in separate repositories with a suffix matching the name of the job which makes sure the image is there. Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-11-12 01:13:28 +08:00
variables:
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
ARCH: arm64
KERNEL_IMAGE_NAME: Image
KERNEL_IMAGE_TYPE: "type:\ image"
BOOT_METHOD: u-boot
ci: Use a single template for LAVA jobs It's a pain to keep both templates in sync and there aren't really that many differences. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9950>
2021-02-01 18:42:43 +08:00
LAVA_TEST_SCRIPT: "/install/deqp-runner.sh"
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
extends:
ci/lava: Switch LAVA jobs to x86 runners So we don't need to provision aarch64 servers, which are these days rarer than x8_64. In the switch to the new runner tags, switch to one which contains the device type, so we can dimension the runner jobs taking into account the number of DUTs available. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11108>
2021-05-31 15:03:04 +08:00
- .use-arm_build # for same $MESA_ARTIFACTS_TAG as in kernel+rootfs_arm64
- .use-x86_build
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
- .lava-test
ci: Use a single kernel+rootfs for both baremetal and LAVA jobs Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-13 13:40:36 +08:00
- .use-kernel+rootfs-arm
gitlab-ci: Replay traces on lava devices Submit lava jobs to replay traces on Veyron (Mali T760) and Kevin (Mali T860) boards. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-By: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5472>
2020-01-28 22:19:53 +08:00
dependencies:
- meson-arm64
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
needs:
gitlab-ci: Fix needs: of the arm64 LAVA test jobs They were still depending on arm_build, but the build of kernel and rootfs has been moved to a separate job. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-By: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5472>
2020-07-13 23:20:28 +08:00
- kernel+rootfs_arm64
ci/lava: Switch LAVA jobs to x86 runners So we don't need to provision aarch64 servers, which are these days rarer than x8_64. In the switch to the new runner tags, switch to one which contains the device type, so we can dimension the runner jobs taking into account the number of DUTs available. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11108>
2021-05-31 15:03:04 +08:00
- x86_build
gitlab-ci: Consolidate container and build stages for LAVA Use the normal build job to also prepare the artifacts for LAVA jobs. For that, the build container needs to also build the test suites, kernel, ramdisk, etc. Then the build job will place the just-built Mesa in the ramdisk and the test job can generate a LAVA job and point to those artifacts. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3295>
2019-12-17 18:50:14 +08:00
- meson-arm64
gitlab-ci/lava: Test Lima driver with dEQP Run dEQP on boards with Mali 400 and 450 in Baylibre's lab. There's lots of skipped tests because of crashes and undetermined behavior. May be a good idea to run the tests with valgrind and fix any issues found. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Vasily Khoruzhick <anarsoul@gmail.com> Reviewed-by: Neil Armstrong <narmstrong@baylibre.com>
2019-10-06 23:49:56 +08:00
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
.lava-test:amd64:
variables:
ARCH: amd64
KERNEL_IMAGE_NAME: bzImage
KERNEL_IMAGE_TYPE: "type:\ zimage"
BOOT_METHOD: u-boot
ci: Use a single template for LAVA jobs It's a pain to keep both templates in sync and there aren't really that many differences. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9950>
2021-02-01 18:42:43 +08:00
LAVA_TEST_SCRIPT: "/install/deqp-runner.sh"
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
extends:
ci: disentangle tags for containers and artifacts produced by them In order to reduce the amount of building work and network traffic, we use docker caching. For that, we use the MESA_IMAGE_TAG and MESA_BASE_TAG env variables which build the MESA_IMAGE variable to identify different containers. We are also using these tags to identify the cached artifacts produced by other containers when those are part of the underlying OS to run directly in DUTs through the DISTRIBUTION_TAG env variable. The undesirable collateral effect is that we cannot combine a test job using a container which would like to make use of some of the cached artifacts created by another container. In other words, we cannot have a job using a DISTRIBUTION_TAG and a MESA_IMAGE using a different MESA_[IMAGE|BASE]_TAG variables. Now, we split the usage in the DISTRIBUTION_TAG through the definition of MESA_ARTIFACTS_TAG AND MESA_ARTIFACTS_BASE_TAG. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Martin Peres <martin.peres@mupuf.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10977>
2021-05-18 19:14:35 +08:00
- .use-x86_build-base # for same $MESA_ARTIFACTS_BASE_TAG as in kernel+rootfs_amd64
ci/lava: Switch LAVA jobs to x86 runners So we don't need to provision aarch64 servers, which are these days rarer than x8_64. In the switch to the new runner tags, switch to one which contains the device type, so we can dimension the runner jobs taking into account the number of DUTs available. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11108>
2021-05-31 15:03:04 +08:00
- .use-x86_build
ci: Append build image tag to LAVA tag used for minio path This automatically ensures the LAVA kernel / device-tree / rootfs files are updated along with the build image, so any relevant changes in the latter are reflected in the former. v2: * Use the same definition of DISTRIBUTION_TAG in .lava-test:amd64 as in kernel+rootfs_amd64 v3: * Extend comment about $MESA_BASE_TAG in .lava-test:amd64 (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-16 19:17:46 +08:00
- .lava-test
ci: Use a single kernel+rootfs for both baremetal and LAVA jobs Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-13 13:40:36 +08:00
- .use-kernel+rootfs-amd64
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
needs:
- kernel+rootfs_amd64
- meson-testing
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
.lava-traces-base:
ci: Test RadeonSI with piglit's quick_gl And do some job refactoring to share more lines between job definitions. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-07 15:23:13 +08:00
variables:
LAVA_TEST_SCRIPT: "/install/piglit/run.sh"
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
artifacts:
reports:
ci/lava: Return the run's results/ artifacts from the DUTs. Finally LAVA users will be able to see deqp XMLs on failures from the job's artifacts browser. This replaces a couple of one-off minio uploads in the piglit runner. Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10297>
2021-04-17 05:18:07 +08:00
junit: results/junit.xml
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
.lava-piglit:
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
variables:
ci: Test RadeonSI with piglit's quick_gl And do some job refactoring to share more lines between job definitions. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-07 15:23:13 +08:00
LAVA_TEST_SCRIPT: "/install/piglit/piglit-runner.sh"
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
.lava-piglit-traces:amd64:
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
extends:
- .lava-test:amd64
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
- .lava-piglit
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
- .lava-traces-base
ci: Build kernels and rootfs for x86 devices For testing Mesa on LAVA devices with the amd64 architecture, build kernels and rootfs in the same way as we do for arm64 and armhf. Also add a few trivial jobs for a specific AMD Chromebook. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5903>
2020-07-03 16:04:20 +08:00
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
.lava-piglit-traces:armhf:
gitlab-ci: Replay traces on lava devices Submit lava jobs to replay traces on Veyron (Mali T760) and Kevin (Mali T860) boards. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-By: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5472>
2020-01-28 22:19:53 +08:00
extends:
- .lava-test:armhf
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
- .lava-piglit
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
- .lava-traces-base
gitlab-ci: Replay traces on lava devices Submit lava jobs to replay traces on Veyron (Mali T760) and Kevin (Mali T860) boards. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-By: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5472>
2020-01-28 22:19:53 +08:00
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
.lava-piglit-traces:arm64:
gitlab-ci: Replay traces on lava devices Submit lava jobs to replay traces on Veyron (Mali T760) and Kevin (Mali T860) boards. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-By: Rohan Garg <rohan.garg@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5472>
2020-01-28 22:19:53 +08:00
extends:
- .lava-test:arm64
ci: add piglit jobs to LAVA and remove tracie ones v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v2] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-28 03:18:00 +08:00
- .lava-piglit
gitlab-ci: Enable unit test reports for lava traces jobs Download from minio the JUnit XML file that tracie produces and inform gitlab about it, so that the pipeline page can present more detailed information about tracie test results. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6598>
2020-09-04 18:53:41 +08:00
- .lava-traces-base
ci: Test RadeonSI with piglit's quick_gl And do some job refactoring to share more lines between job definitions. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10139>
2021-04-07 15:23:13 +08:00
.lava-piglit:amd64:
extends:
- .lava-test:amd64
- .lava-piglit
Reference in New Issue Copy Permalink