third_party
/
virglrenderer
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2607 Commits
1 Branch
0 Tags
6.6 MiB
Tag: Branch: Tree: a4844ef735
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a4844ef735'
${ noResults }
virglrenderer/.gitlab-ci.yml

285 lines
7.4 KiB
Raw Normal View History Unescape

ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
variables:
FDO_UPSTREAM_REPO: "virgl/virglrenderer"
MESA_TEMPLATES_COMMIT: &ci-templates-commit 290b79e0e78eab67a83766f4e9691be554fc4afd
MESA_BASE_TAG: ${DEBIAN_BASE_TAG}
#
# IMPORTANT!
#
# Use the Pipeline ID corresponding to the Mesa Git rev provided below.
# If multiple pipeline runs are available, please choose the one having
# at least the 'debian-testing' job in 'Build-x86_64' stage completed.
#
ci: Update Mesa Git revision Use a more recent Mesa Git revision & pipeline ID. Additionally, update the expectation files accordingly. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
MESA_PIPELINE_ID: 502781
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
MESA_PROJECT_PATH: mesa/mesa
MINIO_HOST: minio-packet.freedesktop.org
# Per-pipeline artifact storage on MinIO
PIPELINE_ARTIFACTS_BASE: ${MINIO_HOST}/artifacts/${CI_PROJECT_PATH}/${CI_PIPELINE_ID}
CI_REGISTRY_IMAGE: "registry.freedesktop.org/${MESA_PROJECT_PATH}"
include:
- project: 'freedesktop/ci-templates'
ref: 79c325922670137e8f0a4dc5f6f097e0eb57c1af
file:
- '/templates/ci-fairy.yml'
- project: 'freedesktop/ci-templates'
ref: *ci-templates-commit
file:
- '/templates/debian.yml'
- '/templates/fedora.yml'
- project: 'mesa/mesa'
# IMPORTANT: Use a recent Mesa Git revision
ci: Update Mesa Git revision Use a more recent Mesa Git revision & pipeline ID. Additionally, update the expectation files accordingly. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
ref: fa4390f7bf6c2bff7ee6799b67accdf2e2db475c
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
file:
- '/.gitlab-ci/image-tags.yml'
ci: Only run by default when scheduled for merge request VirGL just runs way too many jobs, with each pipeline consuming the entire committed x86-64 build capacity we have available, so we need to restrict it anyway. This is made worse by the fact it will create duplicate pipelines for merge requests. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/744>
3 years ago
# YAML anchors for rule conditions
# --------------------------------
.rules-anchors:
rules:
# Scheduled pipeline
- if: &is-scheduled-pipeline '$CI_PIPELINE_SOURCE == "schedule"'
when: on_success
# For Marge Bot
- if: &is-for-marge '$GITLAB_USER_LOGIN == "marge-bot"'
when: never
# Forked project branch
- if: &is-forked-branch '$CI_PROJECT_NAMESPACE != "virgl" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
when: manual
# Forked project branch / pre-merge pipeline not for Marge bot
- if: &is-forked-branch-or-pre-merge-not-for-marge '$CI_PROJECT_NAMESPACE != "virgl" || ($GITLAB_USER_LOGIN != "marge-bot" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $CI_COMMIT_REF_NAME)'
when: manual
# Pipeline runs for the main branch of the upstream virglrenderer project
- if: &is-virglrenderer-main '$CI_PROJECT_NAMESPACE == "virgl" && $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_DEFAULT_BRANCH'
when: always
# Post-merge pipeline
- if: &is-post-merge '$CI_PROJECT_NAMESPACE == "virgl" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
when: on_success
# Post-merge pipeline, not for Marge Bot
- if: &is-post-merge-not-for-marge '$CI_PROJECT_NAMESPACE == "virgl" && $GITLAB_USER_LOGIN != "marge-bot" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
when: on_success
# Pre-merge pipeline
- if: &is-pre-merge '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $CI_COMMIT_REF_NAME'
when: on_success
# Pre-merge pipeline for Marge Bot
- if: &is-pre-merge-for-marge '$GITLAB_USER_LOGIN == "marge-bot" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $CI_COMMIT_REF_NAME'
when: on_success
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
stages:
- build
- sanity test
- test
.set-image:
variables:
MESA_IMAGE: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${MESA_IMAGE_TAG}--${MESA_TEMPLATES_COMMIT}"
image: "$MESA_IMAGE"
.set-image-base-tag:
extends:
- .set-image
variables:
MESA_IMAGE: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${MESA_IMAGE_TAG}--${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
debian/x86_build:
stage: build
extends:
- .set-image-base-tag
variables:
MESA_IMAGE_PATH: ${DEBIAN_X86_BUILD_IMAGE_PATH}
MESA_IMAGE_TAG: ${DEBIAN_BUILD_TAG}
MINIO_ARTIFACT_NAME: virgl-amd64
script:
- .gitlab-ci/meson/build.sh
artifacts:
name: "virgl_${CI_JOB_NAME}"
when: always
paths:
- install/
- results/
ci: Only run by default when scheduled for merge request VirGL just runs way too many jobs, with each pipeline consuming the entire committed x86-64 build capacity we have available, so we need to restrict it anyway. This is made worse by the fact it will create duplicate pipelines for merge requests. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/744>
3 years ago
rules:
- if: *is-scheduled-pipeline
when: on_success
- if: *is-post-merge
when: never
- if: *is-forked-branch-or-pre-merge-not-for-marge
when: manual
- if: *is-pre-merge-for-marge
when: on_success
- when: manual
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
#
# Sanity test jobs
#
.make_check_base:
stage: sanity test
extends: debian/x86_build
CI: Switch dependencies to needs I remembered wrong; needs is the good new one, and dependencies is the bad old one. Flip all the jobs over to using needs instead. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/748>
3 years ago
needs: []
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
artifacts:
when: always
paths:
- results/
mesa check meson:
extends: .make_check_base
variables:
TEST_SUITE: make-check-meson
make check clang-fuzzer:
extends: .make_check_base
variables:
TEST_SUITE: make-check-clang-fuzzer
CC: clang
EXTRA_OPTION: "-D fuzzer=true"
make check trace-stderr:
extends: .make_check_base
variables:
TEST_SUITE: make-check-trace-stderr
EXTRA_OPTION: "-D tracing=stderr"
make check venus:
extends: .make_check_base
variables:
TEST_SUITE: make-check-venus
EXTRA_OPTION: "-D venus-experimental=true"
#
# Piglit & dEQP test jobs
#
.use-gl-test-image:
stage: test
extends:
- .set-image-base-tag
variables:
MESA_IMAGE_PATH: ${DEBIAN_X86_TEST_IMAGE_PATH}
MESA_IMAGE_TAG: ${DEBIAN_X86_TEST_GL_TAG}
script:
- .gitlab-ci/container/debian/x86_test.sh
artifacts:
name: "virgl_${CI_JOB_NAME}"
when: always
paths:
- results/
reports:
junit: results/junit.xml
CI: Switch dependencies to needs I remembered wrong; needs is the good new one, and dependencies is the bad old one. Flip all the jobs over to using needs instead. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/748>
3 years ago
needs:
- job: debian/x86_build
artifacts: true
ci: Only run by default when scheduled for merge request VirGL just runs way too many jobs, with each pipeline consuming the entire committed x86-64 build capacity we have available, so we need to restrict it anyway. This is made worse by the fact it will create duplicate pipelines for merge requests. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/744>
3 years ago
rules:
ci: Don't run post-merge test jobs We mark the build job as never running post-merge, because we just don't want a pipeline running. GitLab seems to respond to this by just trying to run the job anyway, so mark it as never. In all other cases, it will be run on_success when the upstream jobs it depends on have completed. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/748>
3 years ago
- if: *is-post-merge
when: never
ci: Only run by default when scheduled for merge request VirGL just runs way too many jobs, with each pipeline consuming the entire committed x86-64 build capacity we have available, so we need to restrict it anyway. This is made worse by the fact it will create duplicate pipelines for merge requests. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/744>
3 years ago
- when: on_success
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
.gl-host-test:
extends:
- .use-gl-test-image
variables:
GALLIUM_DRIVER: virpipe
GALLIVM_PERF: nopt
.gl-virt-test:
extends:
- .use-gl-test-image
variables:
GALLIUM_DRIVER: virgl
CROSVM_GALLIUM_DRIVER: llvmpipe
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
GALLIVM_PERF: "nopt,no_quad_lod"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
.deqp-host:
extends:
- .gl-host-test
parallel: 3
.piglit-host:
extends:
- .gl-host-test
variables: &piglit-host-variables
PIGLIT_PLATFORM: surfaceless_egl
PIGLIT_NO_WINDOW: 1
PIGLIT_PROFILES: gpu
parallel: 2
.deqp-virt:
extends:
- .gl-virt-test
variables:
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
# There will be FDO_CI_CONCURRENT Crosvm processes, so each should use a single thread
LP_NUM_THREADS: 1
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
parallel: 3
.piglit-virt:
extends:
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
- .gl-virt-test
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
variables:
<<: *piglit-host-variables
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
# Use all threads for rendering and only run one job at a time
LP_NUM_THREADS: ${FDO_CI_CONCURRENT}
FORCE_FDO_CI_CONCURRENT: 1
parallel: 4
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
# Host runners (virpipe/vtest)
debian/x86_test/deqp-gl-host:
extends:
- .deqp-host
variables:
DEQP_SUITE: virgl-gl
GPU_VERSION: virgl-gl
debian/x86_test/deqp-gles-host:
extends:
- .deqp-host
variables:
VIRGL_HOST_API: GLES
DEQP_SUITE: virgl-gles
GPU_VERSION: virgl-gles
debian/x86_test/piglit-gl-host:
extends:
- .piglit-host
variables:
GPU_VERSION: virgl-gl
debian/x86_test/piglit-gles-host:
extends:
- .piglit-host
variables:
VIRGL_HOST_API: GLES
GPU_VERSION: virgl-gles
# Virt runners (virgl/crosvm)
ci: Enable virtio-gpu test jobs Fix the expectation files for all virtio-gpu jobs and enable them in the CI pipeline. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
debian/x86_test/deqp-gl-virt:
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
extends:
- .deqp-virt
variables:
DEQP_SUITE: virgl-gl
GPU_VERSION: virgl-gl
CROSVM_GPU_ARGS: &deqp-gl-crosvm-gpu-args "gles=false,backend=virglrenderer,egl=true,surfaceless=true,width=1024,height=768"
ci: Enable virtio-gpu test jobs Fix the expectation files for all virtio-gpu jobs and enable them in the CI pipeline. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
debian/x86_test/deqp-gles-virt:
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
extends:
- .deqp-virt
variables:
VIRGL_HOST_API: GLES
DEQP_SUITE: virgl-gles
GPU_VERSION: virgl-gles
CROSVM_GPU_ARGS: &deqp-gles-crosvm-gpu-args "gles=true,backend=virglrenderer,egl=true,surfaceless=true,width=1024,height=768"
ci: Enable virtio-gpu test jobs Fix the expectation files for all virtio-gpu jobs and enable them in the CI pipeline. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
debian/x86_test/piglit-gl-virt:
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
extends:
- .piglit-virt
variables:
GPU_VERSION: virgl-gl
CROSVM_GPU_ARGS: *deqp-gl-crosvm-gpu-args
ci: Enable virtio-gpu test jobs Fix the expectation files for all virtio-gpu jobs and enable them in the CI pipeline. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
debian/x86_test/piglit-gles-virt:
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
extends:
- .piglit-virt
variables:
VIRGL_HOST_API: GLES
GPU_VERSION: virgl-gles
CROSVM_GPU_ARGS: *deqp-gles-crosvm-gpu-args