mirrors/mesa
0
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2024-11-27 04:04:23 +08:00
Code Issues Packages Projects Releases Wiki Activity
8992cf5ab8
mesa/.gitlab-ci.yml

1365 lines
38 KiB
YAML
Raw Normal View History

gitlab-ci: add ubuntu container Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:21:45 +08:00
variables:
ci: Update the ci-templates commit. There has been a big rename of variables in the upstream repo to make it clear what's being handed to ci-templates. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4099>
2020-03-07 05:23:20 +08:00
FDO_UPSTREAM_REPO: mesa/mesa
ci: Update to latest ci-templates This is possible again thanks to https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955 , and this MR requires rebuilding all templates based docker images anyway, so we can pull in the latest templates for free. We need to exclude /dev/* when unpacking rootfs tarballs for the arm_test image, since x86 container build jobs do not allow mknod anymore with current templates. The baremetal test jobs have another filesystem mounted on /dev anyway. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-04-01 17:56:17 +08:00
MESA_TEMPLATES_COMMIT: &ci-templates-commit 290b79e0e78eab67a83766f4e9691be554fc4afd
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
CI_PRE_CLONE_SCRIPT: |-
set -o xtrace
CI: Don't stream wget directly into bash If our environment has pipefail set, bash could exit early before wget has completed, and we will die with a broken pipe. Work around this by first downloading from wget, and then executing from bash. Signed-off-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14036>
2021-12-03 15:07:47 +08:00
wget -q -O download-git-cache.sh ${CI_PROJECT_URL}/-/raw/${CI_COMMIT_SHA}/.gitlab-ci/download-git-cache.sh
bash download-git-cache.sh
rm download-git-cache.sh
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
set +o xtrace
ci: specify MinIO's host URL in a global variable Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-24 04:32:40 +08:00
MINIO_HOST: minio-packet.freedesktop.org
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-pipeline artifact storage on MinIO
PIPELINE_ARTIFACTS_BASE: ${MINIO_HOST}/artifacts/${CI_PROJECT_PATH}/${CI_PIPELINE_ID}
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
# per-job artifact storage on MinIO
JOB_ARTIFACTS_BASE: ${PIPELINE_ARTIFACTS_BASE}/${CI_JOB_ID}
ci/piglit: Fix path to uploaded images Missed this bit when I was reworking environment variables. Signed-off-by: Daniel Stone <daniels@collabora.com> Reported-by: Emma Anholt <emma@anholt.net> Ref: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11329#note_956187 Acked-by: Martin Peres <martin.peres@mupuf.org> Acked-by: Emma Anholt <emma@anholt.net> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11337>
2021-06-12 17:19:36 +08:00
# reference images stored for traces
PIGLIT_REPLAY_REFERENCE_IMAGES_BASE: "${MINIO_HOST}/mesa-tracie-results/$FDO_UPSTREAM_REPO"
freedreno/ci: Add a status variable for CI farm Make it a one-line change to disable freedreno CI jobs if the farm is offline. Signed-off-by: Rob Clark <robdclark@chromium.org> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12602>
2021-08-28 01:06:16 +08:00
# Individual CI farm status, set to "offline" to disable jobs
# running on a particular CI farm (ie. for outages, etc):
freedreno/ci: Bring fd farm back online after move Signed-off-by: Rob Clark <robdclark@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12608>
2021-08-28 22:56:05 +08:00
FD_FARM: "online"
CI: use wayland ci-templates repo to create the base image There shouldn't be a difference for users, but this way we do manage all of our containers from freedesktop.org note: compared to the provious Dockerfile, we need to manually add gcc, g++ and python*-wheel Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-04-02 15:24:00 +08:00
ci: Use ci-fairy minio login via token file For every CI job, put JWT content into a file and unset CI_JOB_JWT environment var ======= * virgl jobs: - Share JWT token file to crosvm instance - Keep using `export -p` due to high complexity in the scripts of these jobs. At least, the CI_JOB_JWT will not be leaked, since it is being unset at the `before_script` phase of each Mesa CI job. * iris jobs: Update lava_job_submitter to take token file as argument - generate-env with CI_JOB_JWT_TOKEN_FILE - create token file during baremetal init stage * baremetal jobs: Copy token file to bare-metal NFS Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:13:10 +08:00
default:
before_script:
- echo -e "\e[0Ksection_start:$(date +%s):unset_env_vars_section[collapsed=true]\r\e[0KUnsetting vulnerable environment variables"
- export CI_JOB_JWT_FILE="${CI_JOB_JWT_FILE:-$(mktemp)}"
- echo -n "${CI_JOB_JWT}" > "${CI_JOB_JWT_FILE}"
- unset CI_JOB_JWT
- echo -e "\e[0Ksection_end:$(date +%s):unset_env_vars_section\r\e[0K"
after_script:
- >
set +x
test -e "${CI_JOB_JWT_FILE}" &&
export CI_JOB_JWT="$(<${CI_JOB_JWT_FILE})" &&
rm "${CI_JOB_JWT_FILE}"
CI: use wayland ci-templates repo to create the base image There shouldn't be a difference for users, but this way we do manage all of our containers from freedesktop.org note: compared to the provious Dockerfile, we need to manually add gcc, g++ and python*-wheel Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-04-02 15:24:00 +08:00
include:
ci: Update the ci-templates commit. There has been a big rename of variables in the upstream repo to make it clear what's being handed to ci-templates. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4099>
2020-03-07 05:23:20 +08:00
- project: 'freedesktop/ci-templates'
ci: Update ci-fairy to version with --token-file support Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-11-05 11:13:01 +08:00
ref: 34f4ade99434043f88e164933f570301fd18b125
ci: Drop ci-templates-sha anchor As of GitLab 13.6, multiple files can be included for a single ref. Suggested-by: Daniel Stone <daniel@fooishbar.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-25 00:02:13 +08:00
file:
ci: Use ci-fairy docker image instead of local git_archive one The ci-fairy image contains pip and ci-fairy. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:23:29 +08:00
- '/templates/ci-fairy.yml'
ci: Go back to previous ci-templates commit for debian.yml The newer commit broke the arm64_test container build. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3910 v2: * Also bump all image tags which had been bumped in the meantime Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7883>
2020-12-03 00:37:16 +08:00
- project: 'freedesktop/ci-templates'
ci: Fix MESA_TEMPLATES_COMMIT value The intention was to set it to the commit used for debian.yml, but I accidentally set it to the ci-fairy.yml commit instead. v2: * While we're at it, put two dashes between the base tag and the ci-templates commit hash, making them easier to tell apart. v3: * While we're at it, fix the year of some recently bumped tags. Fixes: 48f78dfd1ac1 "ci: Define global variable MESA_TEMPLATES_COMMIT for ci-templates commit" Reviewed-by: Eric Anholt <eric@anholt.net> # v2 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8690>
2020-12-16 01:02:04 +08:00
ref: *ci-templates-commit
ci: Go back to previous ci-templates commit for debian.yml The newer commit broke the arm64_test container build. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3910 v2: * Also bump all image tags which had been bumped in the meantime Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7883>
2020-12-03 00:37:16 +08:00
file:
ci: Drop ci-templates-sha anchor As of GitLab 13.6, multiple files can be included for a single ref. Suggested-by: Daniel Stone <daniel@fooishbar.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-25 00:02:13 +08:00
- '/templates/debian.yml'
ci: Add Fedora 34 based x86 build docker image v2: * Do not install weak dependencies in Fedora docker image. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-05-12 22:42:37 +08:00
- '/templates/fedora.yml'
ci/lava: Move LAVA files to lava/ Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11309>
2021-06-10 18:10:10 +08:00
- local: '.gitlab-ci/lava/lava-gitlab-ci.yml'
gitlab-ci: rules:changes to test on tested drivers changes For now tests only use these drivers: * llvmpipe * softpipe * freedreno * lima * etnaviv * panfrost So using rules:changes gitlab feature to run the tests when the changes made are potentially affecting these drivers. A few notes: * the following code: .piglit-test: extends: - .test-gl - .llvmpipe-rules makes gitlab replace .test-gl "rules:changes" values by the one from ".llvmpipe-rules". * rules:changes always matches for non-MR new branches so jobs will always be created (and they'll be run if their dependencies are run). For pushes to existing branches the files changed by the push are used to match the rules:changes path. * the same gitlab feature could be used for some build jobs Acked-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2569> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/2569>
2019-10-31 03:39:08 +08:00
- local: '.gitlab-ci/test-source-dep.yml'
ci: Move specific driver testing to separate files in separate dirs. The top-level gitlab-ci.yml is big and unwieldy when one wants to work on CI for a single driver. Move the drivers to separate include files for ease of finding all your driver's tests, and also to pave the way for work on a single driver's CI to not retest all other drivers. Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9139>
2021-02-19 03:12:56 +08:00
- local: 'src/amd/ci/gitlab-ci.yml'
Revert "ci: disable Broadcom CI" Our POE switch rebooted with factory settings. So devices weren't turning on/off because of failing SMNP auth. This reverts commit 87cdcf56455b78b0ca799adccb20c7d23d1b3a51. Reviewed-by: Iago Toral Quiroga <itoral@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11906>
2021-07-15 19:11:17 +08:00
- local: 'src/broadcom/ci/gitlab-ci.yml'
ci/bare-metal: add etnaviv Add deqp gles2 CI run for GC2000. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.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/12852>
2020-06-12 19:23:44 +08:00
- local: 'src/etnaviv/ci/gitlab-ci.yml'
ci: Move specific driver testing to separate files in separate dirs. The top-level gitlab-ci.yml is big and unwieldy when one wants to work on CI for a single driver. Move the drivers to separate include files for ease of finding all your driver's tests, and also to pave the way for work on a single driver's CI to not retest all other drivers. Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9139>
2021-02-19 03:12:56 +08:00
- local: 'src/freedreno/ci/gitlab-ci.yml'
ci/crocus: Add support for manual CI runs on my G41. Uses a shared runner at my house so we have an easy way to minimally test crocus. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14238>
2021-11-24 03:25:41 +08:00
- local: 'src/gallium/drivers/crocus/ci/gitlab-ci.yml'
CI/windows: Move D3D12 test YML to D3D12 driver folder Reviewed-by: Enrico Galli <enrico.galli@intel.com> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13902>
2021-11-21 22:38:20 +08:00
- local: 'src/gallium/drivers/d3d12/ci/gitlab-ci.yml'
ci/i915g: Introduce manual testing of i915g using anholt's runner. Now you can mash the button to see how badly i915g's broken these days. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10874>
2021-05-18 06:06:34 +08:00
- local: 'src/gallium/drivers/i915/ci/gitlab-ci.yml'
ci/lava: Move the per-driver gitlab-ci.yml to each driver. Follow-up to !9139, will cause less testing of other drivers when changing the CI configuration for a single driver. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9353>
2021-03-02 04:50:51 +08:00
- local: 'src/gallium/drivers/iris/ci/gitlab-ci.yml'
- local: 'src/gallium/drivers/lima/ci/gitlab-ci.yml'
ci: Move specific driver testing to separate files in separate dirs. The top-level gitlab-ci.yml is big and unwieldy when one wants to work on CI for a single driver. Move the drivers to separate include files for ease of finding all your driver's tests, and also to pave the way for work on a single driver's CI to not retest all other drivers. Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9139>
2021-02-19 03:12:56 +08:00
- local: 'src/gallium/drivers/llvmpipe/ci/gitlab-ci.yml'
ci/lava: Move the per-driver gitlab-ci.yml to each driver. Follow-up to !9139, will cause less testing of other drivers when changing the CI configuration for a single driver. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9353>
2021-03-02 04:50:51 +08:00
- local: 'src/gallium/drivers/radeonsi/ci/gitlab-ci.yml'
ci: Move specific driver testing to separate files in separate dirs. The top-level gitlab-ci.yml is big and unwieldy when one wants to work on CI for a single driver. Move the drivers to separate include files for ease of finding all your driver's tests, and also to pave the way for work on a single driver's CI to not retest all other drivers. Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9139>
2021-02-19 03:12:56 +08:00
- local: 'src/gallium/drivers/softpipe/ci/gitlab-ci.yml'
- local: 'src/gallium/drivers/virgl/ci/gitlab-ci.yml'
- local: 'src/gallium/drivers/zink/ci/gitlab-ci.yml'
ci/lavapipe: split out lavapipe ci into lavapipe dir there's no need to run llvmpipe jobs if only lavapipe has changed Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9695>
2021-03-19 03:58:04 +08:00
- local: 'src/gallium/frontends/lavapipe/ci/gitlab-ci.yml'
CI/windows: Move SPIRV-to-DXIL test YML to microsoft folder Reviewed-by: Enrico Galli <enrico.galli@intel.com> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13902>
2021-11-21 22:41:37 +08:00
- local: 'src/microsoft/ci/gitlab-ci.yml'
panfrost/ci: Move CI files to src/panfrost In preparation for testing panvk. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Alyssa Rosenzweig <alyssa@collabora.com> Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13016>
2021-07-05 15:25:57 +08:00
- local: 'src/panfrost/ci/gitlab-ci.yml'
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
gitlab-ci: add ubuntu container Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:21:45 +08:00
stages:
ci: Move sanity stage to the beginning of the pipeline This is possible now that it uses the external ci-fairy docker image. This allows dropping the "check mr" job from needs: of other jobs, the container stage jobs will only become available once the sanity stage has passed. This also allows simplifying the "check mr" job rules and script, since the job only needs to exist in pre-merge pipelines for MRs anymore. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:32:05 +08:00
- sanity
ci: Move test-docs job to deploy stage We put it in the first container stage to prevent it from waiting for jobs in previous stages, but empty needs: works for that as well. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:10:08 +08:00
- container
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
- git-archive
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- build-x86_64
CI: Collapse SCons & meson-misc stages into one This is now called 'build-misc'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
- build-misc
CI: Collapse radv & radeonsi stages into one This is now called 'amd'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
- amd
gitlab-ci: add intel APL and GLK devices with manual triggers This add support for the Intel Apollo Lake and Gemini Lake families, however the job will be disabled by default unless the developer manually hit play for the iris-apl-traces and iris-glk-traces jobs in GitLab CI. These devices are still under experimental level support in the Lava lab and are not guaranteed to work reliably yet. Once they become reliable and more resilient we will enable them by default in MesaCI. Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8162>
2020-12-18 11:40:02 +08:00
- intel
CI: Collapse lima & panfrost stages into one This is now called 'arm'; even though they're two separate drivers, it does help cut down on some of the more egregious horizontal scrolling. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
- arm
ci/vc4: rename stage to Broadcom It fits better with what other drivers has done. Signed-off-by: Juan A. Suarez Romero <jasuarez@igalia.com> Acked-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8702>
2021-01-25 19:33:52 +08:00
- broadcom
CI: Collapse lima & panfrost stages into one This is now called 'arm'; even though they're two separate drivers, it does help cut down on some of the more egregious horizontal scrolling. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
- freedreno
ci/bare-metal: add etnaviv Add deqp gles2 CI run for GC2000. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.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/12852>
2020-06-12 19:23:44 +08:00
- etnaviv
CI: Reorder non-hardware stages last Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:57:47 +08:00
- software-renderer
CI: Collapse virgl & d3d12 stages into one This is now called 'layered-backends'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
- layered-backends
ci: Move deploy stage to the end of the pipeline This should make more important jobs visible without scrolling on pipeline pages. The deploy stage jobs only depend on the sanity job or none at all, so this has no impact on when the former can run. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7926>
2020-12-05 17:15:38 +08:00
- deploy
gitlab-ci: add ubuntu container Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:21:45 +08:00
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
# Generic rule to not run the job during scheduled pipelines
# ----------------------------------------------------------
.scheduled_pipelines-rules:
rules: &ignore_scheduled_pipelines
ci: Add "is scheduled pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:44:40 +08:00
if: &is-scheduled-pipeline '$CI_PIPELINE_SOURCE == "schedule"'
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
when: never
ci: Add "is master branch of main project" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:20:39 +08:00
# YAML anchors for rule conditions
# --------------------------------
.rules-anchors:
rules:
ci: Add "is for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-09 00:00:21 +08:00
# For Marge Bot
- if: &is-for-marge '$GITLAB_USER_LOGIN == "marge-bot"'
when: never
ci: Add "is forked branch" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:52:24 +08:00
# Forked project branch
ci: Always use CI_PROJECT_NAMESPACE instead of CI_PROJECT_PATH And always check it first. Cleanup for consistency. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-09 00:02:58 +08:00
- if: &is-forked-branch '$CI_PROJECT_NAMESPACE != "mesa" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
ci: Add "is forked branch" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:52:24 +08:00
when: manual
gitlab-ci: rule anchor for experimental devices as manual in MRs We want to give developers the option to run their jobs on devices that are still being stabilized in the CI infrastructure. These jobs should be optional and not prevent merging from happening. The is-forked-branch-or-pre-merge anchor was not being used anywhere, so it was changed to is-forked-branch-or-pre-merge-not-for-marge to create this new rule. Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10405>
2021-04-22 19:17:40 +08:00
# Forked project branch / pre-merge pipeline not for Marge bot
- if: &is-forked-branch-or-pre-merge-not-for-marge '$CI_PROJECT_NAMESPACE != "mesa" || ($GITLAB_USER_LOGIN != "marge-bot" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $CI_COMMIT_REF_NAME)'
ci: Add "is forked branch or pre-merge pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:30:49 +08:00
when: manual
.gitlab-ci.yml: Use main branch for gitlab ci Reworks: * Fix mesa/mesamaster typo to mesa/mesa main (anholt) * Use $CI_DEFAULT_BRANCH (eric_engestrom) Signed-off-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2021-04-27 04:16:55 +08:00
# Pipeline runs for the main branch of the upstream Mesa project
- if: &is-mesa-main '$CI_PROJECT_NAMESPACE == "mesa" && $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_DEFAULT_BRANCH'
ci: Add "is master branch of main project" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:20:39 +08:00
when: always
ci: Add "is post-merge pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:47:18 +08:00
# Post-merge pipeline
- if: &is-post-merge '$CI_PROJECT_NAMESPACE == "mesa" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
when: on_success
ci: Add "is post-merge pipeline, not for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:36:11 +08:00
# Post-merge pipeline, not for Marge Bot
ci: Always use CI_PROJECT_NAMESPACE instead of CI_PROJECT_PATH And always check it first. Cleanup for consistency. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-09 00:02:58 +08:00
- if: &is-post-merge-not-for-marge '$CI_PROJECT_NAMESPACE == "mesa" && $GITLAB_USER_LOGIN != "marge-bot" && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME != $CI_COMMIT_REF_NAME'
ci: Add "is post-merge pipeline, not for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:36:11 +08:00
when: on_success
ci: Add "is pre-merge pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:58:32 +08:00
# Pre-merge pipeline
- if: &is-pre-merge '$CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == $CI_COMMIT_REF_NAME'
when: on_success
ci: Add "is pre-merge pipeline for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:31:08 +08:00
# 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: Add "is master branch of main project" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:20:39 +08:00
ci: test docs for non-master builds This ensures that we test on CI before merge-requests gets merged. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:10:29 +08:00
.docs-base:
ci: Use ci-fairy docker image instead of local git_archive one The ci-fairy image contains pip and ci-fairy. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:23:29 +08:00
extends:
- .fdo.ci-fairy
- .ci-run-policy
gitlab-ci: build and deploy docs Dunno if alpine is a good idea. It's what the gitlab docs use for most of their examples, so that's what I've gone with... Can probably be changed to something else if wanted. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4630>
2019-05-27 23:12:10 +08:00
script:
docs: Begin documenting ISL This commit mostly just adds the framework required to scrape documentation out of the ISL sources and headers. The method chosen here is a combination of doxygen and breathe (a sphinx extension for doxygen integration). I'll freely admit that doxygen is pretty terrible but it seems like the best option we have available to us today. Acked-by: Emma Anholt <emma@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com>. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11366>
2021-06-15 05:55:21 +08:00
- apk --no-cache add graphviz doxygen
- pip3 install "sphinx<4.0" breathe mako sphinx_rtd_theme
- docs/doxygen-wrapper.py --out-dir=docs/doxygen_xml
ci: turn sphinx-build warnings into errors This should make it harder to accidentally introduce formatting issues into the docs. Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9914>
2021-03-30 18:46:49 +08:00
- sphinx-build -W -b html docs public
ci: test docs for non-master builds This ensures that we test on CI before merge-requests gets merged. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:10:29 +08:00
pages:
extends: .docs-base
ci: move test-docs to container stage While we're at it, rename it to reflect that we're now also testing docs here. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:10:40 +08:00
stage: deploy
gitlab-ci: build and deploy docs Dunno if alpine is a good idea. It's what the gitlab docs use for most of their examples, so that's what I've gone with... Can probably be changed to something else if wanted. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4630>
2019-05-27 23:12:10 +08:00
artifacts:
paths:
- public
ci: Add empty needs: to pages job So it doesn't need to wait for jobs in earlier stages. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:12:11 +08:00
needs: []
gitlab-ci: Extend .ci-run-policy template for docs jobs Requires using rules: in the pages job as well, so it doesn't inherit the rules from the template. v2: * Add comment explaining that cases not covered by explicit rules default to "when: never". Reviewed-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:21:06 +08:00
rules:
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
- *ignore_scheduled_pipelines
.gitlab-ci.yml: Use main branch for gitlab ci Reworks: * Fix mesa/mesamaster typo to mesa/mesa main (anholt) * Use $CI_DEFAULT_BRANCH (eric_engestrom) Signed-off-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2021-04-27 04:16:55 +08:00
- if: *is-mesa-main
gitlab-ci: Extend .ci-run-policy template for docs jobs Requires using rules: in the pages job as well, so it doesn't inherit the rules from the template. v2: * Add comment explaining that cases not covered by explicit rules default to "when: never". Reviewed-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:21:06 +08:00
changes: &docs-or-ci
- docs/**/*
- .gitlab-ci.yml
ci: Use "when: always" for pages job "when: on_success" meant that that the job wouldn't run automatically until all jobs of all earlier stages passed, and would be skipped if any of them failed. But we need to always run this job if any documentation files were modified. Fixes: 8e2cb8ef276b "gitlab-ci: Extend .ci-run-policy template for docs jobs" Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5711>
2020-07-01 23:41:06 +08:00
when: always
gitlab-ci: Extend .ci-run-policy template for docs jobs Requires using rules: in the pages job as well, so it doesn't inherit the rules from the template. v2: * Add comment explaining that cases not covered by explicit rules default to "when: never". Reviewed-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:21:06 +08:00
# Other cases default to never
gitlab-ci: add ubuntu container Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:21:45 +08:00
ci: test docs for non-master builds This ensures that we test on CI before merge-requests gets merged. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:10:29 +08:00
test-docs:
extends: .docs-base
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
ci: Move test-docs job to deploy stage We put it in the first container stage to prevent it from waiting for jobs in previous stages, but empty needs: works for that as well. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:10:08 +08:00
stage: deploy
ci: Run sanity job only in pre-merge pipelines It's more of a nuisance than useful for forked branches. This means the test-docs job can no longer have a direct dependency on sanity for forked branches, so split it up into two jobs: one for pre-merge pipelines, one for forked branches. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7926>
2020-12-04 01:25:54 +08:00
needs: []
rules:
- *ignore_scheduled_pipelines
- if: *is-forked-branch
changes: *docs-or-ci
when: manual
# Other cases default to never
test-docs-mr:
extends:
- test-docs
ci: Make test-docs job depend on sanity job Without this, the test-docs job could end up waiting for manual action after the sanity job failed, which prevented the pipeline as a whole from having failed status. (This means the test-docs job will no longer exist in one corner case where it did before, when pushing directly to a non-master branch of the main repository. That should be fine, since the docs are only deployed from master.) Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-20 18:05:56 +08:00
needs:
- sanity
CI: always expose docs artifacts This makes it easier to preview docs changes in merge-requests. Also make sure we build the docs right away, rather than waiting for when marge merges. This allows us to see the artifacts right away. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8398>
2021-01-09 05:08:56 +08:00
artifacts:
expose_as: 'Documentation preview'
paths:
ci: Add trailing slash to path for documentation preview Fixes the documentation preview link on the MR Overview tab. Found by comparing with the same thing in weston. (It still appears only after all jobs in the pipeline have at least started once though) Fixes: ae8f9584f4c9 "CI: always expose docs artifacts" Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8927>
2021-02-10 19:20:25 +08:00
- public/
gitlab-ci: Use rules: instead of except:/only: for test-docs job Only run the job automatically for Marge Bot, otherwise let it be triggered manually. v2: * Never run this job for the main project, since it's only needed in pre-merge pipelines. * Add comment explaining that cases not covered by explicit rules default to "when: never". Reviewed-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:13:05 +08:00
rules:
ci: Run sanity job only in pre-merge pipelines It's more of a nuisance than useful for forked branches. This means the test-docs job can no longer have a direct dependency on sanity for forked branches, so split it up into two jobs: one for pre-merge pipelines, one for forked branches. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7926>
2020-12-04 01:25:54 +08:00
- if: *is-pre-merge
ci: Do not create manual test-docs job in post-merge pipelines Only in pre-merge pipelines for MRs, or in pipelines for forked project branches. Having the manual job in post-merge pipelines prevented the pages job from running automatically as well, which could prevent the public website from getting updated. Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6534>
2020-09-01 17:44:54 +08:00
changes: *docs-or-ci
CI: always expose docs artifacts This makes it easier to preview docs changes in merge-requests. Also make sure we build the docs right away, rather than waiting for when marge merges. This allows us to see the artifacts right away. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8398>
2021-01-09 05:08:56 +08:00
when: on_success
gitlab-ci: Use rules: instead of except:/only: for test-docs job Only run the job automatically for Marge Bot, otherwise let it be triggered manually. v2: * Never run this job for the main project, since it's only needed in pre-merge pipelines. * Add comment explaining that cases not covered by explicit rules default to "when: never". Reviewed-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:13:05 +08:00
# Other cases default to never
ci: test docs for non-master builds This ensures that we test on CI before merge-requests gets merged. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5469>
2020-06-22 17:10:29 +08:00
gitlab-ci: always run the containers build If the first time a fork was created, the job creating the containers was manually cancelled, this would have left the fork unable to use the CI (until the next automatic regeneration of the container). Avoid this by always running the container-generation job, even though 99% of the time it will spin up, see that the container exists and shut down. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
2019-02-22 23:52:08 +08:00
# When to automatically run the CI
gitlab-ci: Use multiple inheritance instead of YAML references Support for multiple inheritance was added to GitLab recently. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-06 23:35:52 +08:00
.ci-run-policy:
gitlab-ci: Overhaul job run policy Use new rules: instead of only: For container stage jobs: * In the main Mesa project, run them by default. * In merge requests, run them by default if any files affecting pipeline results are changed. * In all other cases (in particular branches in personal projects), don't run them by default but allow triggering them manually. build & test stage jobs are left at the default (when: on_success), so they will run automatically once all their dependencies are satisified. (Using the same rules as above would require these jobs to be manually triggered as well, which is only possible once all dependency jobs have passed) Please be considerate of CI runner resources and cancel unneeded jobs on personal branches with no corresponding merge requests (this can be done before the jobs start running). In summary: No more special branch names. Unnecessary job runs are avoided by default, but jobs which don't run by default can be triggered manually. v2: * Split out LAVA changes to separate commit * Clarify commit log a little, in particular WRT build/test stage jobs Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> # v1 Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> # v1 Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> # v1 Acked-by: Eric Engestrom <eric.engestrom@intel.com>
2019-09-26 15:27:27 +08:00
rules:
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
- *ignore_scheduled_pipelines
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
# If any files affecting the pipeline are changed, build/test jobs run
# automatically once all dependency jobs have passed
- changes: &all_paths
gitlab-ci: Stop using manual jobs for merge requests They were causing trouble with Marge Bot: The project settings require that the pipeline succeeds before a merge request (MR) can be merged, otherwise Marge doesn't wait for the pipeline to succeed before merging an MR assigned to her. But Marge can't start manual jobs, so she would always time out waiting for pipelines with manual jobs. To avoid this, use these rules: * Run the pipeline by default for MRs and main project branches changing any files affecting it. * For other MRs, run a single dummy job which always succeeds. * Don't run any jobs for main project branch changes (e.g. from an MR having been merged) not affecting the pipeline. * Allow jobs to be started manually on branches of forked projects, as before. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361>
2020-01-13 16:45:57 +08:00
- VERSION
gitlab-ci: exclude scripts that don't affect the build All the other files in bin/ are not used by any build system and as such cannot affect the build. I've been working on maintainer tools lately and it's frustrating to have the CI wait for 45 minutes to rebuild everything and not even read/run the files in the MR when it could've just been merged and moved on to the next MR 45 minutes ago. Signed-off-by: Eric Engestrom <eric@engestrom.ch> Acked-by: Tapani Pälli <tapani.palli@intel.com> Reviewed-by: Dylan Baker <dylan@pnwbakers.com> Reviewed-by: Jose Fonseca <jfonseca@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5046>
2020-05-15 04:51:38 +08:00
- bin/git_sha1_gen.py
- bin/install_megadrivers.py
- bin/meson_get_version.py
- bin/symbols-check.py
gitlab-ci: Stop using manual jobs for merge requests They were causing trouble with Marge Bot: The project settings require that the pipeline succeeds before a merge request (MR) can be merged, otherwise Marge doesn't wait for the pipeline to succeed before merging an MR assigned to her. But Marge can't start manual jobs, so she would always time out waiting for pipelines with manual jobs. To avoid this, use these rules: * Run the pipeline by default for MRs and main project branches changing any files affecting it. * For other MRs, run a single dummy job which always succeeds. * Don't run any jobs for main project branch changes (e.g. from an MR having been merged) not affecting the pipeline. * Allow jobs to be started manually on branches of forked projects, as before. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361>
2020-01-13 16:45:57 +08:00
# GitLab CI
- .gitlab-ci.yml
- .gitlab-ci/**/*
# Meson
- meson*
- build-support/**/*
- subprojects/**/*
# Source code
- include/**/*
- src/**/*
when: on_success
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
# Otherwise, build/test jobs won't run
gitlab-ci: Stop using manual jobs for merge requests They were causing trouble with Marge Bot: The project settings require that the pipeline succeeds before a merge request (MR) can be merged, otherwise Marge doesn't wait for the pipeline to succeed before merging an MR assigned to her. But Marge can't start manual jobs, so she would always time out waiting for pipelines with manual jobs. To avoid this, use these rules: * Run the pipeline by default for MRs and main project branches changing any files affecting it. * For other MRs, run a single dummy job which always succeeds. * Don't run any jobs for main project branch changes (e.g. from an MR having been merged) not affecting the pipeline. * Allow jobs to be started manually on branches of forked projects, as before. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361>
2020-01-13 16:45:57 +08:00
- when: never
gitlab-ci: Automatically retry jobs after runner system failure Up to twice, for a total of 3 attempts maximum. This will hopefully avoid spurious CI pipeline failures due to intermittent GitLab/docker infrastructure issues. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-03-27 01:39:41 +08:00
retry:
max: 2
when:
- runner_system_failure
gitlab-ci: always run the containers build If the first time a fork was created, the job creating the containers was manually cancelled, this would have left the fork unable to use the CI (until the next automatic regeneration of the container). Avoid this by always running the container-generation job, even though 99% of the time it will spin up, see that the container exists and shut down. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
2019-02-22 23:52:08 +08:00
gitlab-ci: Stop using manual jobs for merge requests They were causing trouble with Marge Bot: The project settings require that the pipeline succeeds before a merge request (MR) can be merged, otherwise Marge doesn't wait for the pipeline to succeed before merging an MR assigned to her. But Marge can't start manual jobs, so she would always time out waiting for pipelines with manual jobs. To avoid this, use these rules: * Run the pipeline by default for MRs and main project branches changing any files affecting it. * For other MRs, run a single dummy job which always succeeds. * Don't run any jobs for main project branch changes (e.g. from an MR having been merged) not affecting the pipeline. * Allow jobs to be started manually on branches of forked projects, as before. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3361>
2020-01-13 16:45:57 +08:00
gitlab-ci: Use multiple inheritance instead of YAML references Support for multiple inheritance was added to GitLab recently. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-06 23:35:52 +08:00
.ci-deqp-artifacts:
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +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}"
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +08:00
when: always
untracked: false
paths:
# Watch out! Artifacts are relative to the build dir.
# https://gitlab.com/gitlab-org/gitlab-ce/commit/8788fb925706cad594adf6917a6c5f6587dd1521
- artifacts
ci: Ensure that jobs inherting the ci-deqp jobs artifact meson logs Since gitlab-ci cannot merge artifact lists, and the last entry a job extends from overwrites the artifact list, we should ensure that we artifact meson logs via the .ci-deqp-artifacts job. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8937>
2021-02-10 00:43:35 +08:00
- _build/meson-logs/*.txt
ci: Run meson tests in strace if it's available and can be used Keep the strace logs in job artifacts for tests which timed out. This can be useful for figuring out why a timeout occurred. strace cannot be used in jobs where ASAN is enabled, because ASAN's leak checker also uses ptrace(), which isn't possible within strace. Suggested-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-04 19:58:56 +08:00
- _build/meson-logs/strace
gitlab-ci: always run the containers build If the first time a fork was created, the job creating the containers was manually cancelled, this would have left the fork unable to use the CI (until the next automatic regeneration of the container). Avoid this by always running the container-generation job, even though 99% of the time it will spin up, see that the container exists and shut down. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
2019-02-22 23:52:08 +08:00
ci: Move FDO_DISTRIBUTION_TAG assignment to template This will be useful in more places later. Should have no functional effect for now. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:35:45 +08:00
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
# Docker image tag helper templates
ci: Move FDO_DISTRIBUTION_TAG assignment to template This will be useful in more places later. Should have no functional effect for now. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:35:45 +08:00
.incorporate-templates-commit:
variables:
FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_TEMPLATES_COMMIT}"
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
.incorporate-base-tag+templates-commit:
variables:
FDO_BASE_IMAGE: "${CI_REGISTRY_IMAGE}/${MESA_BASE_IMAGE}:${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
.set-image:
ci: Use FDO_DISTRIBUTION_TAG where possible This allows for de duplicating some variables. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12750>
2021-09-07 21:58:45 +08:00
extends:
- .incorporate-templates-commit
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
variables:
ci: Use FDO_DISTRIBUTION_TAG where possible This allows for de duplicating some variables. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12750>
2021-09-07 21:58:45 +08:00
MESA_IMAGE: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${FDO_DISTRIBUTION_TAG}"
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
image: "$MESA_IMAGE"
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
.set-image-base-tag:
extends:
- .set-image
- .incorporate-base-tag+templates-commit
variables:
ci: Use FDO_DISTRIBUTION_TAG where possible This allows for de duplicating some variables. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12750>
2021-09-07 21:58:45 +08:00
MESA_IMAGE: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${FDO_DISTRIBUTION_TAG}"
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
ci: Move FDO_DISTRIBUTION_TAG assignment to template This will be useful in more places later. Should have no functional effect for now. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:35:45 +08:00
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
# Build the CI docker images.
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
#
ci: Append $MESA_TEMPLATES_COMMIT to image tags This ensures all images get rebuilt when we update to a newer ci-templates commit. v2: * Append to WINDOWS(_UPSTREAM)_IMAGE instead of WINDOWS_TAG. The latter failed, apparently variables are not expanded recursively on the Windows runners. * Use separate MESA_IMAGE_TAG/MESA_BASE_IMAGE variables instead of appending to each FDO_DISTRIBUTION_TAG/FDO_BASE_IMAGE separately for Linux jobs, to prevent accidentally dropping the suffix. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7902>
2020-12-04 00:54:05 +08:00
# MESA_IMAGE_TAG is the tag of the docker image used by later stage jobs. If the
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
# image doesn't exist yet, the container stage job generates it.
#
# In order to generate a new image, one should generally change the tag.
# While removing the image from the registry would also work, that's not
# recommended except for ephemeral images during development: Replacing
# an image after a significant amount of time might pull in newer
# versions of gcc/clang or other packages, which might break the build
# with older commits using the same tag.
#
# After merging a change resulting in generating a new image to the
# main repository, it's recommended to remove the image from the source
# repository's container registry, so that the image from the main
# repository's registry will be used there as well.
gitlab-ci: Create separate docker images for Debian stretch & buster Pros: * Less fragile due to not mixing packages from stretch and buster * No longer need to use third-party LLVM packages * The buster image now uses GCC 8 for C++ as well (previously 6 for C++, 8 for C), allowing to drop some hacks Con: * The stretch image now only uses GCC 6 for C as well as C++ * Need separate jobs for testing old LLVM versions Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-09-06 23:04:47 +08:00
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
.container:
ci: Move test-docs job to deploy stage We put it in the first container stage to prevent it from waiting for jobs in previous stages, but empty needs: works for that as well. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:10:08 +08:00
stage: container
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
extends:
- .ci-run-policy
ci: Move FDO_DISTRIBUTION_TAG assignment to template This will be useful in more places later. Should have no functional effect for now. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:35:45 +08:00
- .incorporate-templates-commit
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
rules:
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
- *ignore_scheduled_pipelines
gitlab-ci: Automatically run pipelines for Marge Bot pre-merge only Marge only merges an MR if the pipeline passed. Running the pipeline again after merging is redundant. v2: * Add rule to ensure docker images are up to date in the main project registry (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5680>
2020-06-29 17:33:13 +08:00
# Run pipeline by default in the main project if any CI pipeline
# configuration files were changed, to ensure docker images are up to date
ci: Add "is post-merge pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:47:18 +08:00
- if: *is-post-merge
gitlab-ci: Automatically run pipelines for Marge Bot pre-merge only Marge only merges an MR if the pipeline passed. Running the pipeline again after merging is redundant. v2: * Add rule to ensure docker images are up to date in the main project registry (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5680>
2020-06-29 17:33:13 +08:00
changes:
- .gitlab-ci.yml
- .gitlab-ci/**/*
when: on_success
gitlab-ci: Run merge request pipelines automatically only for Marge Bot MR pipelines not triggered by Marge Bot can still be triggered manually. Motivation: The main & forked Mesa project CI pipelines combined are currently generating over 1 TB of egress traffic per week. ~80% of this is from pre-merge pipelines. Assuming this corresponds to 4 pre-merge and one post-merge pipeline per MR on average, this change could potentially eliminate up to ~60% of the overall traffic (by preventing 3 of the 4 pre-merge pipelines from running automatically). (Of course, this could be subverted if all jobs of the other pipelines were triggered manually anyway... In most cases, manually triggering just a few jobs should suffice) v2: * $GITLAB_USER_NAME was the wrong variable, $GITLAB_USER_LOGIN should do the trick. Suggested-by: Marek Olšák <maraeo@gmail.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 17:46:12 +08:00
# Run pipeline by default if it was triggered by Marge Bot, is for a
gitlab-ci: Automatically run pipelines for Marge Bot pre-merge only Marge only merges an MR if the pipeline passed. Running the pipeline again after merging is redundant. v2: * Add rule to ensure docker images are up to date in the main project registry (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5680>
2020-06-29 17:33:13 +08:00
# merge request, and any files affecting the pipeline were changed
ci: Add "is pre-merge pipeline for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:31:08 +08:00
- if: *is-pre-merge-for-marge
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
changes:
*all_paths
when: on_success
gitlab-ci: Automatically run pipelines for Marge Bot pre-merge only Marge only merges an MR if the pipeline passed. Running the pipeline again after merging is redundant. v2: * Add rule to ensure docker images are up to date in the main project registry (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5680>
2020-06-29 17:33:13 +08:00
# Run pipeline by default in the main project if it was not triggered by
# Marge Bot, and any files affecting the pipeline were changed
ci: Add "is post-merge pipeline, not for Marge Bot" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 18:36:11 +08:00
- if: *is-post-merge-not-for-marge
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
changes:
*all_paths
when: on_success
gitlab-ci: Automatically run pipelines for Marge Bot pre-merge only Marge only merges an MR if the pipeline passed. Running the pipeline again after merging is redundant. v2: * Add rule to ensure docker images are up to date in the main project registry (Eric Anholt) Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5680>
2020-06-29 17:33:13 +08:00
# Allow triggering jobs manually in other cases if any files affecting the
# pipeline were changed
gitlab-ci: Run merge request pipelines automatically only for Marge Bot MR pipelines not triggered by Marge Bot can still be triggered manually. Motivation: The main & forked Mesa project CI pipelines combined are currently generating over 1 TB of egress traffic per week. ~80% of this is from pre-merge pipelines. Assuming this corresponds to 4 pre-merge and one post-merge pipeline per MR on average, this change could potentially eliminate up to ~60% of the overall traffic (by preventing 3 of the 4 pre-merge pipelines from running automatically). (Of course, this could be subverted if all jobs of the other pipelines were triggered manually anyway... In most cases, manually triggering just a few jobs should suffice) v2: * $GITLAB_USER_NAME was the wrong variable, $GITLAB_USER_LOGIN should do the trick. Suggested-by: Marek Olšák <maraeo@gmail.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 17:46:12 +08:00
- changes:
gitlab-ci: Don't require triggering build/test jobs manually Let them run automatically once all their dependencies have passed. Reviewed-by: Adam Jackson <ajax@redhat.com> Acked-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4432>
2020-04-03 18:50:11 +08:00
*all_paths
when: manual
# Otherwise, container jobs won't run
- when: never
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
variables:
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
FDO_DISTRIBUTION_VERSION: bullseye-slim
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
FDO_REPO_SUFFIX: $CI_JOB_NAME
ci: Use FDO_CI_CONCURRENT as our -j flags when present in the runner env. fd.o has retuned the x86 runners on packet for -j8. Rather than having to tweak our CI every time fd.o decides to rebalance job concurrency, respect what the runner admin has chosen for their builds (this will also be convenient for people with large local runners). Reviewed-by: Michel Dänzer <michel@daenzer.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5669>
2020-06-27 01:59:41 +08:00
FDO_DISTRIBUTION_EXEC: 'env FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash .gitlab-ci/container/${CI_JOB_NAME}.sh'
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
# no need to pull the whole repo to build the container image
GIT_STRATEGY: none
ci: Add .use-base-image template And use it in jobs for images using another Mesa image as their base. Should fix the build of images which don't use another Mesa image as their base (by no longer setting the FDO_BASE_IMAGE variable). Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:51:16 +08:00
.use-base-image:
extends:
- .container
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .incorporate-base-tag+templates-commit
ci: Add .use-base-image template And use it in jobs for images using another Mesa image as their base. Should fix the build of images which don't use another Mesa image as their base (by no longer setting the FDO_BASE_IMAGE variable). Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:51:16 +08:00
# Don't want the .container rules
- .ci-run-policy
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based x86 build image base
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/x86_build-base:
gitlab-ci: Use multiple inheritance instead of YAML references Support for multiple inheritance was added to GitLab recently. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-06 23:35:52 +08:00
extends:
gitlab-ci: Update to current templates The .fdo.container-ifnot-exists template has been replaced by .fdo.container-build. We need to include "debian/" in FDO_REPO_SUFFIX for now, we can drop it for individual images when their tags are bumped if we want. Miscellaneous other goodies this gets us: * The templates now add some labels to images which may be useful for garbage collecting unused tags in the future. * The templates now copy the current tag from the main project registry to the forked project's if it already exists in the latter but points to a different image hash. This will avoid false failures (or passes) due to using the wrong image. Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4286> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4286>
2020-03-24 01:16:07 +08:00
- .fdo.container-build@debian
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
- .container
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:
ci: Update ci-fairy to version with --token-file support Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-11-05 11:13:01 +08:00
MESA_IMAGE_TAG: &debian-x86_build-base "2021-11-25-ci-fairy"
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/x86_build-base:
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
extends:
ci: Add .use-base-image template And use it in jobs for images using another Mesa image as their base. Should fix the build of images which don't use another Mesa image as their base (by no longer setting the FDO_BASE_IMAGE variable). Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:51:16 +08:00
- .fdo.container-build@debian
- .use-base-image
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
variables:
ci: Move BASE_TAG expansion to FDO_BASE_IMAGE assignment This fixes the build of images which use another Mesa image as the base. v2: * Move $CI_REGISTRY_IMAGE expansion into FDO_BASE_IMAGE assignment as well (Dave Airlie) Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Reported-by: Dave Airlie <airlied@redhat.com> Acked-by: Eric Anholt <eric@anholt.net> # v1 Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:35:53 +08:00
MESA_BASE_IMAGE: "debian/x86_build-base"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
MESA_ARTIFACTS_BASE_TAG: *debian-x86_build-base
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_build-base
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based x86 main build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/x86_build:
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
gitlab-ci: Add x86_build-base docker image Similar to x86_test-base. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-30 21:53:41 +08:00
variables:
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-x86_build "2021-11-25-libdrm"
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/x86_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
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:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/x86_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-x86_build
gitlab-ci: Add .use-debian-10 template It simplifies the definitions of jobs using the Debian 10 image. The needs: was previously missing from the llvmpipe/softpipe test jobs, so they could spuriously run if the debian-10 job failed or was cancelled. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-10-10 21:27:17 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_build
gitlab-ci: Add .use-debian-10 template It simplifies the definitions of jobs using the Debian 10 image. The needs: was previously missing from the llvmpipe/softpipe test jobs, so they could spuriously run if the debian-10 job failed or was cancelled. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-10-10 21:27:17 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based i386 cross-build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/i386_build:
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-i386_build "2021-11-25-libdrm"
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/i386_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/i386_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-i386_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/i386_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based ppc64el cross-build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/ppc64el_build:
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-ppc64el_build "2021-11-25-libdrm"
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/ppc64el_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/ppc64el_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-ppc64el_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/ppc64el_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based s390x cross-build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/s390x_build:
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-s390x_build "2021-11-25-libdrm"
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/s390x_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/s390x_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-s390x_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/s390x_build
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
# Android NDK cross-build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/android_build:
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
variables:
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-android_build "2021-11-25-libdrm"
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/android_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_build-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/android_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-android_build
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/android_build
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based x86 test image base
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/x86_test-base:
extends: debian/x86_build-base
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
variables:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
MESA_IMAGE_TAG: &debian-x86_test-base "2021-12-02-piglit"
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/x86_test-base:
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
extends:
ci: Add .use-base-image template And use it in jobs for images using another Mesa image as their base. Should fix the build of images which don't use another Mesa image as their base (by no longer setting the FDO_BASE_IMAGE variable). Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:51:16 +08:00
- .fdo.container-build@debian
- .use-base-image
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
variables:
ci: Move BASE_TAG expansion to FDO_BASE_IMAGE assignment This fixes the build of images which use another Mesa image as the base. v2: * Move $CI_REGISTRY_IMAGE expansion into FDO_BASE_IMAGE assignment as well (Dave Airlie) Fixes: 0781d9825b31 "ci: Append $MESA_TEMPLATES_COMMIT to image tags" Reported-by: Dave Airlie <airlied@redhat.com> Acked-by: Eric Anholt <eric@anholt.net> # v1 Reviewed-by: Andres Gomez <agomez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7957>
2020-12-07 16:35:53 +08:00
MESA_BASE_IMAGE: "debian/x86_test-base"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_test-base
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_test-base
gitlab-ci: x86_test-base image as common base for x86_test-gl/vk Making use of the relatively recent FDO_BASE_IMAGE feature of the templates, the x86_test-base image contents are shared as a separate layer by the x86_test-gl/vk images (meaning the former only needs to be downloaded once for either or both of the latter). This should be more efficient in terms of overall network bandwidth and storage, in particular if the base image changes less often than the -gl/vk ones. v2: * List x86_test-base in needs: along with x86_test-gl/vk (see parent commit) * Always put $STABLE/TESTING_EPHEMERAL on separate lines, will make it easier to add any non-ephemeral packages Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5186>
2020-05-16 23:17:23 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based x86 test image for GL
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/x86_test-gl:
extends: .use-debian/x86_test-base
gitlab-ci: Use separate docker images for x86 build/test jobs Same as was done for the ARM images before. This should make it less painful to update to newer dEQP / piglit as well as to make changes to the build/test environment. Reviewed-by: Eric Anholt <eric@anholt.net>
2019-11-06 01:52:24 +08:00
variables:
ci: Move Kernel build tasks into its own file Allows to reuse the Kernel build tasks everywhere it is needed. The x86_test-gl container now need a kernel image to use for the crosvm environment, Reuse this task there. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10862>
2021-03-08 21:05:08 +08:00
FDO_DISTRIBUTION_EXEC: 'env KERNEL_URL=${KERNEL_URL} FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash .gitlab-ci/container/${CI_JOB_NAME}.sh'
ci: Update linux kernel to v5.15 * Update Kconfig for x86_64 and ARM64. Follow the dependency tree of the kernel modules to make sure that the intended configurations are being set. Check scripts/merge_config.sh output as well to see if there is a requested Kconfig not being considered. For a630 devices: * Use kernel version with a6xx workaround for frequency scaling * Enable CONFIG_QCOM_LMH targeting a630 slowness on new kernel ---- Out of tree patches used ---- For a360 device: * Revert a commit which remove slpi_region from msm8996: 8b0031f8bda2 ("Revert "arm64: msm8996: fix memory region overlap"") Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13089>
2021-10-14 00:25:08 +08:00
KERNEL_URL: &kernel-rootfs-url "https://gitlab.freedesktop.org/gfx-ci/linux/-/archive/v5.15-for-mesa-ci-540a4af22d71/linux-v5.15-for-mesa-ci-540a4af22d71.tar.bz2"
ci: Update ci-fairy to version with --token-file support Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-11-05 11:13:01 +08:00
MESA_IMAGE_TAG: &debian-x86_test-gl "2021-11-25-ci-fairy"
gitlab-ci: Use separate docker images for x86 build/test jobs Same as was done for the ARM images before. This should make it less painful to update to newer dEQP / piglit as well as to make changes to the build/test environment. Reviewed-by: Eric Anholt <eric@anholt.net>
2019-11-06 01:52:24 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based x86 test image for VK
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/x86_test-vk:
extends: .use-debian/x86_test-base
gitlab-ci: add a new job that builds a base test image for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:23:18 +08:00
variables:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
MESA_IMAGE_TAG: &debian-x86_test-vk "2021-12-02-piglit"
gitlab-ci: add a new job that builds a base test image for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:23:18 +08:00
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# Debian 11 based ARM build image
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/arm_build:
gitlab-ci: Use multiple inheritance instead of YAML references Support for multiple inheritance was added to GitLab recently. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-06 23:35:52 +08:00
extends:
ci: Update to latest ci-templates This is possible again thanks to https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955 , and this MR requires rebuilding all templates based docker images anyway, so we can pull in the latest templates for free. We need to exclude /dev/* when unpacking rootfs tarballs for the arm_test image, since x86 container build jobs do not allow mknod anymore with current templates. The baremetal test jobs have another filesystem mounted on /dev anyway. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-04-01 17:56:17 +08:00
- .fdo.container-build@debian
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
- .container
ci: Update to latest ci-templates This is possible again thanks to https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955 , and this MR requires rebuilding all templates based docker images anyway, so we can pull in the latest templates for free. We need to exclude /dev/* when unpacking rootfs tarballs for the arm_test image, since x86 container build jobs do not allow mknod anymore with current templates. The baremetal test jobs have another filesystem mounted on /dev anyway. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-04-01 17:56:17 +08:00
tags:
- aarch64
freedreno: Introduce gitlab-based CI. Since freedreno's kernel and GPU reset seem to be totally solid, we don't need to have the complexity of the LAVA setup that panfrost has. Instead, we can register some boards as shared gitlab runners and have the jobs run out of a docker container just like we do for llvmpipe. Just make sure that the DRI device node is passed through to the containers in the gitlab config ('devices = ["/dev/dri"]' under runners.docker). If a runner fails (networking dies, kernel panic, etc.) it'll take out one build but the rest can keep going since gitlab-runner is what pulls jobs. Since the runner pulls jobs, it also means that they can live behind firewalls instead of needing some public address to be accessed by gitlab.fd.o. For now, enable it just on db410c (A307) and cheza (A630) as those are the hardware that I have plenty of. A307 is only testing GLES2 since running all of GLES3 takes too long for the number of boards I've brought up. Acked-by: Rob Clark <robdclark@chromium.org> Acked-by: Kenneth Graunke <kenneth@whitecape.org>
2019-06-29 07:35:32 +08:00
variables:
ci: Update ci-fairy to version with --token-file support Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-11-05 11:13:01 +08:00
MESA_IMAGE_TAG: &debian-arm_build "2021-11-25-ci-fairy"
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
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/arm_build:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
- .set-image
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:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/arm_build"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-arm_build
MESA_ARTIFACTS_TAG: *debian-arm_build
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
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/arm_build
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
ci: Add Fedora 34 based x86 build docker image v2: * Do not install weak dependencies in Fedora docker image. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-05-12 22:42:37 +08:00
# Fedora 34 based x86 build image
fedora/x86_build:
extends:
- .fdo.container-build@fedora
- .container
variables:
FDO_DISTRIBUTION_VERSION: 34
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &fedora-x86_build "2021-11-25-libdrm"
ci: Add Fedora 34 based x86 build docker image v2: * Do not install weak dependencies in Fedora docker image. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-05-12 22:42:37 +08:00
.use-fedora/x86_build:
extends:
- .set-image
variables:
MESA_IMAGE_PATH: "fedora/x86_build"
MESA_IMAGE_TAG: *fedora-x86_build
needs:
- fedora/x86_build
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
.kernel+rootfs:
extends:
- .ci-run-policy
ci: Put all container related jobs in a single stage GitLab 14.2 supports dependencies between jobs in the same stage. Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12790>
2021-09-09 18:26:39 +08:00
stage: container
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
variables:
GIT_STRATEGY: fetch
ci: Move Kernel build tasks into its own file Allows to reuse the Kernel build tasks everywhere it is needed. The x86_test-gl container now need a kernel image to use for the crosvm environment, Reuse this task there. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10862>
2021-03-08 21:05:08 +08:00
KERNEL_URL: *kernel-rootfs-url
ci: Build skqp on ARM64 images This commit makes `kernel+rootfs_arm64` job build and install skqp on ARM64 devices rootfs. Skia repository has a tool to prepare skqp models located at `tools/skqp/cut-release`, which get files from [Skia Gold](https://skia.org/docs/dev/testing/skiagold/), generate files.checksum, rendertests.txt and unittests.txt. One gives a range of commits to let `cut-release` find the right resources to prepare skqp for the user. However, it is failing, since it fails when trying to get image packages from a range of commits via HTTPS from the host https://public-gold.skia.org but it responds with error 404 every time. I tried a range a thousand of commits, yet it still does not give results. The workaround employed was to recover the most recent `files.checksum` and `rendertests.txt` files from the git history and generate `unittests.txt` from `list_gpu_unit_tests` binary. `skqp` runs two lists of tests, `rendertests.txt` and `unittests.txt`. Both must be located inside the `skqp` assets folder. The first list uses GL and GLES to test rendering scenarios. The second runs some unit tests that do not render an image per se. In order to make the first `a630_skqp` to be green, the crashing tests were removed from the test lists and the expectations of the failing ones were updated. It is worth noting that `rendertests.txt` can bring some detail about each test expectation, so each test can have a max pixel error count, to tell `skqp` that it is OK to have at most that number of errors for that test. See also: https://github.com/google/skia/blob/main/tools/skqp/README_ALGORITHM.md As each render backend has a different error count, two different `rendertests.txt` files were created, `src/freedreno/ci/freedreno-a630-skqp-gl_rendertests.txt`, `src/freedreno/ci/freedreno-a630-skqp-gles_rendertests.txt` and , which one refers to GL and GLES tests respectfully. The unit tests file for a630 is located at `src/freedreno/ci/freedreno-a630-skqp_unittests.txt` ``` aaclip domain formats highcontrastfilter rectangle_texture yuv_make_color_space ``` ``` ProcessorOptimizationValidationTest VkProtectedContext_CreateNonprotectedContext VkYCbcrSampler_DrawImageWithYcbcrSampler VkYCbcrSampler_NoYcbcrSurface ``` Each test was updated with the max_error count equal to the first run result. ``` analytic_antialias_inverse async_rescale_and_read_dog_down async_rescale_and_read_dog_up async_rescale_and_read_rose async_rescale_and_read_text_down async_rescale_and_read_text_up async_rescale_and_read_text_up_large async_rescale_and_read_yuv420_rose complexclip2_path_bw encode-platform imageblur_large lcdtextsize onebadarc onefailarc scale-pixels surfaceprops textfilter_color textfilter_image ``` Considering all the following tests results as wrong. ``` async_rescale_and_read_no_bleed backdrop_imagefilter_croprect_persp complexclip2 imageblurrepeatmode mixerCF overdrawcolorfilter patch_alpha patch_primitive rrect_clip_bw scaledemoji_rendering yuv_splitter ``` v2: a) add link to HTML report on job log b) remove extraneous spaces diff c) remove unnecessary conditions from build-skqp.sh d) use fixed skqp source commit SHA v3: a) Use only main skia repository to fetch models and build skqp b) Use list_gpu_unit_tests binary to create a base unittests.txt file c) Remove crashing tests d) Set failing tests expectations for the first skqp run v4: a) Remove clang dependency b) Separate each skqp backend result into its folder c) Regroup a630_skqp in one job v5: a) Separate tests files per driver Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5580 Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14146>
2021-12-07 22:13:00 +08:00
MESA_ROOTFS_TAG: &kernel-rootfs "2021-12-22-skqp"
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
DISTRIBUTION_TAG: &distribution-tag-arm "${MESA_ROOTFS_TAG}--${MESA_ARTIFACTS_TAG}--${MESA_TEMPLATES_COMMIT}"
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
script:
- .gitlab-ci/container/lava_build.sh
kernel+rootfs_amd64:
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build-base
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
- .kernel+rootfs
image: "$FDO_BASE_IMAGE"
variables:
DEBIAN_ARCH: "amd64"
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
DISTRIBUTION_TAG: &distribution-tag-amd64 "${MESA_ROOTFS_TAG}--${MESA_ARTIFACTS_BASE_TAG}--${MESA_TEMPLATES_COMMIT}"
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
kernel+rootfs_arm64:
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/arm_build
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
- .kernel+rootfs
tags:
- aarch64
variables:
DEBIAN_ARCH: "arm64"
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
kernel+rootfs_armhf:
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
extends:
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
- kernel+rootfs_arm64
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
variables:
DEBIAN_ARCH: "armhf"
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
# Cannot use anchors defined here from included files, so use extends: instead
.use-kernel+rootfs-arm:
variables:
DISTRIBUTION_TAG: *distribution-tag-arm
MESA_ROOTFS_TAG: *kernel-rootfs
.use-kernel+rootfs-amd64:
variables:
DISTRIBUTION_TAG: *distribution-tag-amd64
MESA_ROOTFS_TAG: *kernel-rootfs
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
ci: Merge ARM testing docker images to a single arm_test one The merged image contains kernels & rootfs for both arm64 & armhf baremetal test jobs, and is smaller than either arm{64,hf}_test image before. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-30 18:54:15 +08:00
# x86 image with ARM64 & armhf kernel & rootfs for baremetal testing
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
debian/arm_test:
ci: add arm_test-base docker image Similar to x86_build-base. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5381>
2020-06-08 04:03:34 +08:00
extends:
ci: Merge ARM testing docker images to a single arm_test one The merged image contains kernels & rootfs for both arm64 & armhf baremetal test jobs, and is smaller than either arm{64,hf}_test image before. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-30 18:54:15 +08:00
- .fdo.container-build@debian
- .container
# Don't want the .container rules
- .ci-run-policy
ci: Build ARM baremetal rootfs in native container Doing so in an x86 container via qemu was slow, and started failing recently after updating to a newer qemu version. This also results in smaller arm*_test* docker images, since we need to install fewer Debian packages in them. As a bonus, this turns some piglit tests from fail to pass (Or maybe they'll turn out to be flakes? They've passed at least 3 times in a row). Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-29 21:09:06 +08:00
needs:
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
- kernel+rootfs_arm64
- kernel+rootfs_armhf
ci: Switch the baremetal runner to be an x86 docker image. The runner is an x86 system, so running the ARM image meant doing everything at runtime under qemu, and for the xz of the test rootfs that was quite expensive. Also, we can rebuild x86 images much faster than we can rebuild arm images for container development, which will help unblock some of the other feature parity work I have to do versus the old docker system that cheza is using. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5033>
2020-05-14 02:08:08 +08:00
variables:
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
FDO_DISTRIBUTION_EXEC: 'env ARTIFACTS_PREFIX=https://${MINIO_HOST}/mesa-lava ARTIFACTS_SUFFIX=${MESA_ROOTFS_TAG}--${MESA_ARM_BUILD_TAG}--${MESA_TEMPLATES_COMMIT} CI_PROJECT_PATH=${CI_PROJECT_PATH} FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} FDO_UPSTREAM_REPO=${FDO_UPSTREAM_REPO} bash .gitlab-ci/container/${CI_JOB_NAME}.sh'
ci: Merge ARM testing docker images to a single arm_test one The merged image contains kernels & rootfs for both arm64 & armhf baremetal test jobs, and is smaller than either arm{64,hf}_test image before. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-30 18:54:15 +08:00
FDO_DISTRIBUTION_TAG: "${MESA_IMAGE_TAG}--${MESA_ROOTFS_TAG}--${MESA_ARM_BUILD_TAG}--${MESA_TEMPLATES_COMMIT}"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_ARM_BUILD_TAG: *debian-arm_build
ci: Upgrade to libdrm 2.4.109 Required for being able to use drmGetDeviceFromDevId in the loader. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11248>
2021-11-26 06:16:26 +08:00
MESA_IMAGE_TAG: &debian-arm_test "2021-11-25-libdrm"
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
MESA_ROOTFS_TAG: *kernel-rootfs
ci: Switch the baremetal runner to be an x86 docker image. The runner is an x86 system, so running the ARM image meant doing everything at runtime under qemu, and for the xz of the test rootfs that was quite expensive. Also, we can rebuild x86 images much faster than we can rebuild arm images for container development, which will help unblock some of the other feature parity work I have to do versus the old docker system that cheza is using. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5033>
2020-05-14 02:08:08 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/arm_test:
ci: Merge ARM testing docker images to a single arm_test one The merged image contains kernels & rootfs for both arm64 & armhf baremetal test jobs, and is smaller than either arm{64,hf}_test image before. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-30 18:54:15 +08:00
image: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${MESA_IMAGE_TAG}--${MESA_ROOTFS_TAG}--${MESA_ARM_BUILD_TAG}--${MESA_TEMPLATES_COMMIT}"
ci: add testing for VC4 drivers (Raspberry Pi 3) This tests OpenGL ES 2.0 CTS suite with VC4 drivers, through baremetal Raspberry Pi 3 devices. The devices are connected to a switch that supports Power over Ethernet (PoE), so the devices can be started/stopped through the switch, and also to a host that runs the GitLab runner through serial-to-USB cables, to monitor the devices to know when the testing finishes. The Raspberries uses a network boot, using NFS and TFTP. For the root filesystem, they use the one created in the armhf container. For the kernel/modules case, this is handled externally. Currently it is using the same kernel/modules that come with the Raspberry Pi OS. In future we could build them in the same armhf container. At this moment we only test armhf architecture, as this is the default one suggested by the Raspberry Pi Foundation. In future we could also add testing for arm64 architecture. Finally, for the very rare ocassions where the Raspberry Pi 3 device is booted but no data is received, it retries the testing for a second time, powering off and on the device in the process. v2: - Remove commit that exists capture devcoredump (Eric) - Squash remaining commits in one (Andres) v3: - Add missing boot timeout check (Juan) v4: - Use locks when running the PoE on/off script (Eric) - Use a timeout for serial read (Eric) v5: - Rename stage to "raspberrypi" (Eric) - Bump up arm64_test tag (Eric) v6: - Make serial buffer timeout optional (Juan) Reviewed-by: Eric Anholt <eric@anholt.net> Signed-off-by: Juan A. Suarez Romero <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7628>
2020-11-16 03:57:55 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_ARM_BUILD_TAG: *debian-arm_build
ci: Merge ARM testing docker images to a single arm_test one The merged image contains kernels & rootfs for both arm64 & armhf baremetal test jobs, and is smaller than either arm{64,hf}_test image before. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9955>
2021-03-30 18:54:15 +08:00
MESA_IMAGE_PATH: "debian/arm_test"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-arm_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
MESA_ROOTFS_TAG: *kernel-rootfs
ci: add testing for VC4 drivers (Raspberry Pi 3) This tests OpenGL ES 2.0 CTS suite with VC4 drivers, through baremetal Raspberry Pi 3 devices. The devices are connected to a switch that supports Power over Ethernet (PoE), so the devices can be started/stopped through the switch, and also to a host that runs the GitLab runner through serial-to-USB cables, to monitor the devices to know when the testing finishes. The Raspberries uses a network boot, using NFS and TFTP. For the root filesystem, they use the one created in the armhf container. For the kernel/modules case, this is handled externally. Currently it is using the same kernel/modules that come with the Raspberry Pi OS. In future we could build them in the same armhf container. At this moment we only test armhf architecture, as this is the default one suggested by the Raspberry Pi Foundation. In future we could also add testing for arm64 architecture. Finally, for the very rare ocassions where the Raspberry Pi 3 device is booted but no data is received, it retries the testing for a second time, powering off and on the device in the process. v2: - Remove commit that exists capture devcoredump (Eric) - Squash remaining commits in one (Andres) v3: - Add missing boot timeout check (Juan) v4: - Use locks when running the PoE on/off script (Eric) - Use a timeout for serial read (Eric) v5: - Rename stage to "raspberrypi" (Eric) - Bump up arm64_test tag (Eric) v6: - Make serial buffer timeout optional (Juan) Reviewed-by: Eric Anholt <eric@anholt.net> Signed-off-by: Juan A. Suarez Romero <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7628>
2020-11-16 03:57:55 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/arm_test
ci: add testing for VC4 drivers (Raspberry Pi 3) This tests OpenGL ES 2.0 CTS suite with VC4 drivers, through baremetal Raspberry Pi 3 devices. The devices are connected to a switch that supports Power over Ethernet (PoE), so the devices can be started/stopped through the switch, and also to a host that runs the GitLab runner through serial-to-USB cables, to monitor the devices to know when the testing finishes. The Raspberries uses a network boot, using NFS and TFTP. For the root filesystem, they use the one created in the armhf container. For the kernel/modules case, this is handled externally. Currently it is using the same kernel/modules that come with the Raspberry Pi OS. In future we could build them in the same armhf container. At this moment we only test armhf architecture, as this is the default one suggested by the Raspberry Pi Foundation. In future we could also add testing for arm64 architecture. Finally, for the very rare ocassions where the Raspberry Pi 3 device is booted but no data is received, it retries the testing for a second time, powering off and on the device in the process. v2: - Remove commit that exists capture devcoredump (Eric) - Squash remaining commits in one (Andres) v3: - Add missing boot timeout check (Juan) v4: - Use locks when running the PoE on/off script (Eric) - Use a timeout for serial read (Eric) v5: - Rename stage to "raspberrypi" (Eric) - Bump up arm64_test tag (Eric) v6: - Make serial buffer timeout optional (Juan) Reviewed-by: Eric Anholt <eric@anholt.net> Signed-off-by: Juan A. Suarez Romero <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7628>
2020-11-16 03:57:55 +08:00
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
# Native Windows docker builds
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
#
Remove Scons leftovers Fixes: 6e6cd7d93cc54fc8c279 ("scons: Remove.") Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9738>
2021-03-22 01:27:57 +08:00
# Unlike the above Linux-based builds - including MinGW builds which
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
# cross-compile for Windows - which use the freedesktop ci-templates, we
# cannot use the same scheme here. As Windows lacks support for
# Docker-in-Docker, and Podman does not run natively on Windows, we have
# to open-code much of the same ourselves.
#
# This is achieved by first running in a native Windows shell instance
# (host PowerShell) in the container stage to build and push the image,
# then in the build stage by executing inside Docker.
.windows-docker-vs2019:
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
extends:
- .set-image
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
variables:
ci: Do not append ci-templates commit hash to Windows docker image tag We're not using the templates for the Windows image. Fixes needless rebuild of the Windows image when the ci-templates commit is changed. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-04-14 20:34:16 +08:00
MESA_IMAGE: "$CI_REGISTRY_IMAGE/${MESA_IMAGE_PATH}:${MESA_IMAGE_TAG}"
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "windows/x64_build"
CI/windows: Uprev piglit Acked-by: Alyssa Rosenzweig <alyssa@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13893>
2021-11-20 13:12:52 +08:00
MESA_IMAGE_TAG: "2021-11-19-piglit-uprev"
ci: Do not append ci-templates commit hash to Windows docker image tag We're not using the templates for the Windows image. Fixes needless rebuild of the Windows image when the ci-templates commit is changed. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-04-14 20:34:16 +08:00
MESA_UPSTREAM_IMAGE: "$CI_REGISTRY/$FDO_UPSTREAM_REPO/$MESA_IMAGE_PATH:${MESA_IMAGE_TAG}"
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
Revert "CI: Disable Windows jobs" They're fixed now, just in time. This reverts commit 7b44e7d7bb77051913ce24ea177d06820c40304c. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13708>
2021-11-08 21:08:48 +08:00
windows_build_vs2019:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
inherit:
default: false
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
extends:
- .container
- .windows-docker-vs2019
ci: Move test-docs job to deploy stage We put it in the first container stage to prevent it from waiting for jobs in previous stages, but empty needs: works for that as well. Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:10:08 +08:00
stage: container
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
variables:
GIT_STRATEGY: fetch # we do actually need the full repository though
CI: windows: augment the timeout of building the windows container https://gitlab.freedesktop.org/mesa/mesa/-/jobs/6898838 failed at uploading the containers but got kicked out right before being able to give us a valid error. Bump the timeout for windows container builds, to not have this unfortunate situation. Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Daniel Stone <daniel@fooishbar.org> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8740>
2021-01-27 22:21:37 +08:00
timeout: 2h 30m # LLVM + piglit takes ages
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
tags:
- windows
- shell
- "1809"
CI: Avoid htz4 runner for VS2019 The htz4 runner needs to be updated in order for our support binaries like Chocolatey to work. Temporarily restrict jobs to the EC2 runner until this has happened. Signed-off-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4371> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4371>
2020-03-30 17:16:18 +08:00
- mesa
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
script:
ci: Use MESA_ namespace for image variables in Windows jobs Instead of a separate WINDOWS_ namespace. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:42:15 +08:00
- .\.gitlab-ci\windows\mesa_container.ps1 $CI_REGISTRY $CI_REGISTRY_USER $CI_REGISTRY_PASSWORD $MESA_IMAGE $MESA_UPSTREAM_IMAGE
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
.use-windows_build_vs2019:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
inherit:
default: false
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
extends: .windows-docker-vs2019
ci: Use MESA_ namespace for image variables in Windows jobs Instead of a separate WINDOWS_ namespace. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:42:15 +08:00
image: "$MESA_IMAGE"
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
needs:
Revert "CI: Disable Windows/VS2019 builds" DNS is now fixed. This reverts commit 460b8b1758d953b2b820443615d73ccdb1455b5e. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4591>
2020-04-16 21:56:18 +08:00
- windows_build_vs2019
gitlab-ci: set a common job parent for container stage While at it, rename to singular "container" for consistency. Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:04:14 +08:00
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
# Git archive
make git archive:
ci: Use ci-fairy docker image instead of local git_archive one The ci-fairy image contains pip and ci-fairy. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:23:29 +08:00
extends:
- .fdo.ci-fairy
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
stage: git-archive
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
rules:
ci: Add "is scheduled pipeline" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:44:40 +08:00
- if: *is-scheduled-pipeline
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
when: on_success
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
# ensure we are running on packet
tags:
- packet.net
script:
ci: Run git gc before creating Git cache tarball Since the job which creates the cache tarball starts from the previous cache, the cache kept accumulating cruft and growing bigger. This cuts the size of the tarball in half (from almost 600M to under 300M), which can translate to significant time savings when downloading it on some runners. v2: * Use git gc --aggressive (Eric Anholt) Reviewed-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7920>
2020-12-04 21:55:54 +08:00
# Compactify the .git directory
- git gc --aggressive
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
# compress the current folder
- tar -cvzf ../$CI_PROJECT_NAME.tar.gz .
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
# login with the JWT token file
- ci-fairy minio login --token-file "${CI_JOB_JWT_FILE}"
ci: specify MinIO's host URL in a global variable Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-24 04:32:40 +08:00
- ci-fairy minio cp ../$CI_PROJECT_NAME.tar.gz minio://$MINIO_HOST/git-cache/$CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME/$CI_PROJECT_NAME.tar.gz
CI: reduce bandwidth for git pull Over the last 7 days, git pulls represented a total of 1.7 TB. On those 1.7 TB, we can see: - ~300 GB for the CI farm on hetzner - ~730 GB for the CI farm on packet.net - ~680 GB for the rest of the world We can not really change the rest of the world*, but we can certainly reduce the egress costs towards our CI farms. Right now, the gitlab runners are not doing a good job at caching the git trees for the various jobs we make, and we end up with a lot of cache-misses. A typical pipeline ends up with a good 2.8GB of git pull data. (a compressed archive of the mesa folder accounts for 280MB) In this patch, we implemented what was suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/215591#note_334642576 - we host a brand new MinIO server on packet - jobs can upload files on 2 locations: * git-cache/<namespace>/<project>/<branch-name>.tar.gz * artifacts/<namespace>/<project>/<pipeline-id>/ - the authorization is handled by gitlab with short tokens valid only for the time of the job is running - whenever a job runs, the runner are configured to execute (eval) $CI_PRE_CLONE_SCRIPT - this variable is set globally to download the current cache from the MinIO packet server, unpack it and replace the possibly out of date cache found on the runner - then git fetch is run by the runner, and only the delta between the upstream tree and the local tree gets pulled. We can rebuild the git cache in a schedule job (once a day seems sufficient), and then we can stop the cache miss entirely. First results showed that instead of pulling 280MB of data in my fork, I got a pull of only 250KB. That should help us. * arguably, there are other farms in the rest of the world, so hopefully we can change those too. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5428>
2020-06-11 23:16:28 +08:00
ci: Add jobs running ci-fairy checks These can catch various common issues in MR settings and Git commit logs. The "check mr" job only exists in pre-merge pipelines for MRs, and runs automatically. The "check commits" job only exists in pre-merge pipelines for MRs and in pipelines for forked branches. It runs automatically in the former case and can be manually triggered in the latter. v2: * Use git_archive docker image (Daniel Stone) * Use a single sanity stage for both jobs (Tomeu Vizoso) Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:37:33 +08:00
# Sanity checks of MR settings and commit logs
ci: Squash "check mr/commits" jobs into a single sanity job The "check commits" job can work again with current ci-templates, but there's no need to keep it as a separate job. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:48:47 +08:00
sanity:
ci: Use ci-fairy docker image instead of local git_archive one The ci-fairy image contains pip and ci-fairy. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:23:29 +08:00
extends:
- .fdo.ci-fairy
ci: Add jobs running ci-fairy checks These can catch various common issues in MR settings and Git commit logs. The "check mr" job only exists in pre-merge pipelines for MRs, and runs automatically. The "check commits" job only exists in pre-merge pipelines for MRs and in pipelines for forked branches. It runs automatically in the former case and can be manually triggered in the latter. v2: * Use git_archive docker image (Daniel Stone) * Use a single sanity stage for both jobs (Tomeu Vizoso) Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:37:33 +08:00
stage: sanity
rules:
ci: Only run the sanity job if there's a MR As it will fail right away if there isn't, and that prevents the CI to run on people's branches. $ ci-fairy check-merge-request --require-allow-collaboration --junit-xml=check-merge-request.xml ERROR: No open merge request against mesa/mesa with sha 9f6aba4be0ceb59d35732651cc44f676e93b70b5 Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Fixes: d4151f2e ("ci: Run sanity job only in pre-merge pipelines") Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8032>
2020-12-10 19:48:32 +08:00
- if: *is-pre-merge
ci: Add jobs running ci-fairy checks These can catch various common issues in MR settings and Git commit logs. The "check mr" job only exists in pre-merge pipelines for MRs, and runs automatically. The "check commits" job only exists in pre-merge pipelines for MRs and in pipelines for forked branches. It runs automatically in the former case and can be manually triggered in the latter. v2: * Use git_archive docker image (Daniel Stone) * Use a single sanity stage for both jobs (Tomeu Vizoso) Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:37:33 +08:00
when: on_success
# Other cases default to never
ci: sanity job doesn't need the Git tree This should fix the sanity job taking >= 1 minute in some cases. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7904>
2020-12-04 01:58:09 +08:00
variables:
GIT_STRATEGY: none
ci: Add jobs running ci-fairy checks These can catch various common issues in MR settings and Git commit logs. The "check mr" job only exists in pre-merge pipelines for MRs, and runs automatically. The "check commits" job only exists in pre-merge pipelines for MRs and in pipelines for forked branches. It runs automatically in the former case and can be manually triggered in the latter. v2: * Use git_archive docker image (Daniel Stone) * Use a single sanity stage for both jobs (Tomeu Vizoso) Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:37:33 +08:00
script:
ci: disable check-commits Otherwise the CI sanity check fails if the commit title exceed 80 characters Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7852>
2020-12-01 21:27:42 +08:00
# ci-fairy check-commits --junit-xml=check-commits.xml
ci: Squash "check mr/commits" jobs into a single sanity job The "check commits" job can work again with current ci-templates, but there's no need to keep it as a separate job. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7676>
2020-11-19 01:48:47 +08:00
- ci-fairy check-merge-request --require-allow-collaboration --junit-xml=check-merge-request.xml
artifacts:
when: on_failure
reports:
junit: check-*.xml
ci: Add jobs running ci-fairy checks These can catch various common issues in MR settings and Git commit logs. The "check mr" job only exists in pre-merge pipelines for MRs, and runs automatically. The "check commits" job only exists in pre-merge pipelines for MRs and in pipelines for forked branches. It runs automatically in the former case and can be manually triggered in the latter. v2: * Use git_archive docker image (Daniel Stone) * Use a single sanity stage for both jobs (Tomeu Vizoso) Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6209>
2020-08-06 23:37:33 +08:00
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
# BUILD
gitlab-ci: refactor out some common stuff for Windows and Linux Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:21:31 +08:00
# Shared between windows and Linux
.build-common:
gitlab-ci: set a common job parent for build stage Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:52:58 +08:00
extends: .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: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +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}"
gitlab-ci: Only keep the build logs as artifacts. On a build failure, we were tarring up the whole ccache directory, build.ninja, build products, etc. This was over 400MB compressed on a recent early meson-main build failure, which fd.o then has to hang on to for 4 weeks. The build logs are probably the interesting part, are potentially useful regardless ("how did CI's build flags differ from mine?"), and are <500k uncompressed on my personal meson build. Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>
2019-07-25 00:27:48 +08:00
when: always
paths:
- _build/meson-logs/*.txt
ci: Run meson tests in strace if it's available and can be used Keep the strace logs in job artifacts for tests which timed out. This can be useful for figuring out why a timeout occurred. strace cannot be used in jobs where ASAN is enabled, because ASAN's leak checker also uses ptrace(), which isn't possible within strace. Suggested-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-04 19:58:56 +08:00
- _build/meson-logs/strace
gitlab-ci: Add a shader-db run using v3d on drm-shim. This provides significant compiler coverage during CI at a fairly low cost in CPU time (~17s per thread for 4 threads on gst-gitlab-htz-runner3). I'm leaving wget in the docker image, as once this is in master I'm planning on having an automatic shader-db comparison between master and the branch included in the artifacts. I also haven't done freedreno yet, because it has some races when run in multithreaded mode that I'm still tracking down. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-04-11 06:59:12 +08:00
- shader-db
gitlab-ci: refactor out some common stuff for Windows and Linux Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:21:31 +08:00
# Just Linux
.build-linux:
extends: .build-common
gitlab-ci: Install most packages from Debian buster We now use the C frontend of GCC 8 instead of 6 (required tweaking the before_script for the clang job). We cannot use the C++ frontend of GCC 7 or newer yet, because upstream GCC 7 changed some C++ name mangling stuff in backwards incompatible ways, and LLVM < 6.0 packages aren't available in buster. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-04-05 00:01:27 +08:00
variables:
CCACHE_COMPILERCHECK: "content"
gitlab-ci: Directly use host-mapped directory for ccache Use hardcoded /cache/mesa/ccache for the cache, so it will be shared by all jobs of all Mesa projects running on the same runner host. This should increase the hit rate and decrease the worst case storage used. Further benefits of directly using a host-mapped directory: * Saves up to ~1 minute per job for restoring and saving the cache contents via the GitLab CI cache mechanism * Cache contents generated by failed jobs are no longer lost * Jobs running in parallel on the same runner host can get hits from each other Also enable compression, so the default maximum cache size of 5G might be sufficient. v2: * Move CCACHE_DIR variable to the .build-linux template Suggested-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Anholt <eric@anholt.net> # v1
2019-11-20 16:11:35 +08:00
CCACHE_COMPRESS: "true"
CCACHE_DIR: /cache/mesa/ccache
gitlab-ci: use ccache to speed up builds Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-02-13 00:59:27 +08:00
# Use ccache transparently, and print stats before/after
before_script:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
- !reference [default, before_script]
gitlab-ci: use ccache to speed up builds Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-02-13 00:59:27 +08:00
- export PATH="/usr/lib/ccache:$PATH"
- export CCACHE_BASEDIR="$PWD"
gitlab-ci: Directly use host-mapped directory for ccache Use hardcoded /cache/mesa/ccache for the cache, so it will be shared by all jobs of all Mesa projects running on the same runner host. This should increase the hit rate and decrease the worst case storage used. Further benefits of directly using a host-mapped directory: * Saves up to ~1 minute per job for restoring and saving the cache contents via the GitLab CI cache mechanism * Cache contents generated by failed jobs are no longer lost * Jobs running in parallel on the same runner host can get hits from each other Also enable compression, so the default maximum cache size of 5G might be sufficient. v2: * Move CCACHE_DIR variable to the .build-linux template Suggested-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Anholt <eric@anholt.net> # v1
2019-11-20 16:11:35 +08:00
- ccache --show-stats
gitlab-ci: use ccache to speed up builds Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-02-13 00:59:27 +08:00
after_script:
- ccache --show-stats
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
- !reference [default, after_script]
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
gitlab-ci: Add a job for meson on windows This adds a new CI job that runs on windows with MSVC. It currently builds softpipe and osmesa, and runs the related unit tests. It does rely on meson's wraps for zlib, but I've set up caching of the wrap dependencies so hopefully that wont be a problem. I really wanted to user powershell for this, but there just isn't an easy way to do that, it's much easier to use batch scripts, so thats what I used. The leading `/` for .gitlab-ci/lava... must be removed because windows doesn't understand it, and when it reads the file the job ends in error. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:36:19 +08:00
.build-windows:
extends: .build-common
tags:
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
- windows
- docker
- "1809"
CI: Re-enable Windows VS2019 builds The failures are fixed, but I didn't notice this had been silently disabled in !4272. Re-enable the VS2019 build. Signed-off-by: Daniel Stone <daniels@collabora.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4374> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4374>
2020-03-30 22:58:51 +08:00
- mesa
gitlab-ci: Add a job for meson on windows This adds a new CI job that runs on windows with MSVC. It currently builds softpipe and osmesa, and runs the related unit tests. It does rely on meson's wraps for zlib, but I've set up caching of the wrap dependencies so hopefully that wont be a problem. I really wanted to user powershell for this, but there just isn't an easy way to do that, it's much easier to use batch scripts, so thats what I used. The leading `/` for .gitlab-ci/lava... must be removed because windows doesn't understand it, and when it reads the file the job ends in error. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:36:19 +08:00
cache:
key: ${CI_JOB_NAME}
paths:
- subprojects/packagecache
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
.meson-build:
gitlab-ci: set a common job parent for build stage Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:52:58 +08:00
extends:
gitlab-ci: refactor out some common stuff for Windows and Linux Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:21:31 +08:00
- .build-linux
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_build
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
stage: build-x86_64
gitlab-ci: Test against LLVM / clang 9 on x86 They're not available for Debian buster yet, so we have to use upstream snapshot packages again. In contrast to earlier, we now store the LLVM APT repository key in Git instead of re-downloading it every time.
2019-12-13 18:02:16 +08:00
variables:
ci: Bump LLVM/clang from 10 to 11 Preparation for moving to Debian bullseye, which has packages for LLVM 9 & 11, but not 10. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:25:54 +08:00
LLVM_VERSION: 11
gitlab-ci: use ccache to speed up builds Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-02-13 00:59:27 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
gitlab-ci: add a meson vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-20 19:26:53 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-testing:
gitlab-ci: Use multiple inheritance instead of YAML references Support for multiple inheritance was added to GitLab recently. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-06 23:35:52 +08:00
extends:
- .meson-build
- .ci-deqp-artifacts
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "enabled"
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
DRI_LOADERS: >
-D glx=dri
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gbm=enabled
-D egl=enabled
egl: automatically compile the `drm` platform when available Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3161>
2019-06-25 22:44:16 +08:00
-D platforms=x11
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
GALLIUM_ST: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D dri3=enabled
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>
2021-10-09 04:17:27 +08:00
-D gallium-va=enabled
ci/crocus: Add support for manual CI runs on my G41. Uses a shared runner at my house so we have an easy way to minimally test crocus. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14238>
2021-11-24 03:25:41 +08:00
GALLIUM_DRIVERS: "swrast,virgl,radeonsi,zink,crocus,iris,i915"
CI: add lavapipe vulkan testing Acked-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7952>
2020-08-19 11:32:24 +08:00
VULKAN_DRIVERS: "swrast,amd"
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
BUILDTYPE: "debugoptimized"
ci: Enable -Werror on meson-vulkan and meson-testing. I want to make sure that I don't introduce warnings in turnip where we have active work going on, and I also want to make sure that the drivers we care about testing are warnings-clean. As with the previous -Werror change, this is for CI only and doesn't affect end-user builds. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3607> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3607>
2019-12-17 13:23:02 +08:00
EXTRA_OPTION: >
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: Allow better customization of the name of the artifacts for minio. To have asan testing, we need two different sets of artifacts per arch. Plus, "UPLOAD_FOR_LAVA" was misnamed at this point anyway. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2021-02-16 04:35:41 +08:00
MINIO_ARTIFACT_NAME: mesa-amd64
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
- .gitlab-ci/prepare-artifacts.sh
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-testing-asan:
ci: Add an ASan build on x86. I want to enable ASan runs on freedreno. It turns out it's a long road to get there, starting with making sure we can run our unit tests with the sanitizer enabled. While I'm revving this container, add in valgrind too to make sure that our build paths with valgrind enabled work. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7936>
2020-12-01 04:01:23 +08:00
extends:
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-testing
ci: Add an ASan build on x86. I want to enable ASan runs on freedreno. It turns out it's a long road to get there, starting with making sure we can run our unit tests with the sanitizer enabled. While I'm revving this container, add in valgrind too to make sure that our build paths with valgrind enabled work. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7936>
2020-12-01 04:01:23 +08:00
variables:
ci: Enable -Werror for the remaining GCC build jobs Same principle as for clang, with much fewer exceptions left. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10220>
2021-04-11 18:50:36 +08:00
C_ARGS: >
-Wno-error=stringop-truncation
ci: Add an ASan build on x86. I want to enable ASan runs on freedreno. It turns out it's a long road to get there, starting with making sure we can run our unit tests with the sanitizer enabled. While I'm revving this container, add in valgrind too to make sure that our build paths with valgrind enabled work. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7936>
2020-12-01 04:01:23 +08:00
EXTRA_OPTION: >
-D b_sanitize=address
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: Allow better customization of the name of the artifacts for minio. To have asan testing, we need two different sets of artifacts per arch. Plus, "UPLOAD_FOR_LAVA" was misnamed at this point anyway. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2021-02-16 04:35:41 +08:00
MINIO_ARTIFACT_NAME: ""
ci: Add a fractional deqp run of softpipe with asan enabled. This should help us avoid landing memory leaks (and some buffer overflows) throughout the GL stack. I put the asan lib in x86_test-base because we'll want asan for lavapipe, too. This requires keeping debug symbols for the asan drivers in the artifacts, as otherwise you can't do much with the backtraces it produces. Closes: #3726 Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8530>
2021-01-15 01:56:52 +08:00
ARTIFACTS_DEBUG_SYMBOLS: 1
ci: Add an ASan build on x86. I want to enable ASan runs on freedreno. It turns out it's a long road to get there, starting with making sure we can run our unit tests with the sanitizer enabled. While I'm revving this container, add in valgrind too to make sure that our build paths with valgrind enabled work. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7936>
2020-12-01 04:01:23 +08:00
ci: Enable a build with MSan. This will catch uninitialized data usage (such as 37855fd59d18 ("glcpp: Fully initialize struct gl_context")) much faster than valgrind does. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14236>
2021-12-18 02:25:36 +08:00
debian-testing-msan:
extends:
- debian-clang
variables:
# l_undef is incompatible with msan
EXTRA_OPTION:
-D b_sanitize=memory
-D b_lundef=false
MINIO_ARTIFACT_NAME: ""
ARTIFACTS_DEBUG_SYMBOLS: 1
# Don't run all the tests yet:
# GLSL has some issues in sexpression reading.
# gtest has issues in its test initialization.
MESON_TEST_ARGS: "--suite glcpp --suite gallium --suite format"
# Freedreno dropped because freedreno tools fail at msan.
GALLIUM_DRIVERS: "iris,nouveau,kmsro,r300,r600,swrast,svga,v3d,vc4,virgl,etnaviv,panfrost,lima,zink,radeonsi,tegra,d3d12,crocus"
VULKAN_DRIVERS: intel,amd,broadcom,virtio-experimental
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-clover-testing:
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
extends:
- .meson-build
- .ci-deqp-artifacts
variables:
UNWIND: "enabled"
DRI_LOADERS: >
-D glx=disabled
-D egl=disabled
-D gbm=disabled
GALLIUM_ST: >
-D gallium-opencl=icd
-D opencl-spirv=true
GALLIUM_DRIVERS: "swrast"
BUILDTYPE: "debugoptimized"
ci: Enable -Werror in more clover builds. We've slowly been pushing -Werror through the set of CI builds, and it looks like clover is clean at the moment. Keep it that way. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Rob Clark <robdclark@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7664>
2020-11-18 04:06:53 +08:00
EXTRA_OPTION: >
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
- .gitlab-ci/prepare-artifacts.sh
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-gallium:
gitlab-ci: add a job that only build things needed for testing For turnip and RADV testing, we will need a debugoptimized build without UBSAN. This introduces meson-testing which builds only the things that are needed by the test stage. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 19:23:41 +08:00
extends: .meson-build
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "enabled"
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
DRI_LOADERS: >
-D glx=dri
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gbm=enabled
-D egl=enabled
egl: automatically compile the `drm` platform when available Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3161>
2019-06-25 22:44:16 +08:00
-D platforms=x11,wayland
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
GALLIUM_ST: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D dri3=enabled
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
-D gallium-extra-hud=true
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-vdpau=enabled
-D gallium-xvmc=enabled
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
-D gallium-omx=bellagio
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-va=enabled
-D gallium-xa=enabled
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
-D gallium-nine=true
-D gallium-opencl=disabled
gallium/swr: Remove common code and build options This commit removes all OpenSWR references from common Mesa code and build system. Reviewed-by: Dylan Baker <dylan@pnwbakers.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11264>
2021-06-09 20:16:23 +08:00
GALLIUM_DRIVERS: "iris,nouveau,kmsro,r300,r600,freedreno,swrast,svga,v3d,vc4,virgl,etnaviv,panfrost,lima,zink,d3d12,asahi,crocus"
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 14:40:27 +08:00
VULKAN_DRIVERS: swrast
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
EXTRA_OPTION: >
mesa: Retire classic OSMesa. The classic OSMesa renders directly into user memory using src/mesa/swrast, while gallium OSMesa renders using softpipe or llvmpipe and copies out at glFlush() time. This would make gallium look like a worse choice for OSMesa, except that swrast is: 1) Painfully slow to render compared to llvmpipe 2) Incorrect at derivatives 3) Limited to GL 2.1 instead of GL 4.6 In my survey of OSMesa users, debian was the remaining holdout with classic OSMesa in use on hurd and some rare non-LLVM-supported architectures (sh4, alpha, etc.). As of today, they've switched to softpipe-based gallium OSMesa for them. To prevent people from running the wrong OSMesa (to the extent that running OSMesa can ever be the right thing), delete the classic version. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Closes: #320 Closes: #877 Closes: #2297 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1243>
2019-07-04 02:10:32 +08:00
-D osmesa=true
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
-D tools=all
gitlab-ci: Move artifact preparation to separate script It's currently only needed for the meson-main and meson-arm64 jobs, not the other meson build jobs. Also remove MESON_SHADERDB, just run .gitlab-ci/run-shader-db.sh directly from the meson-main job. v2: * Also run prepare-artifacts.sh in meson-arm64 script v3: * Move tarball creation into the new script as well, as it prevented ccache --show-stats from running in after_script Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> # v1 Reviewed-by: Eric Anholt <eric@anholt.net>
2019-10-24 00:42:53 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
gitlab-ci: Move artifact preparation to separate script It's currently only needed for the meson-main and meson-arm64 jobs, not the other meson build jobs. Also remove MESON_SHADERDB, just run .gitlab-ci/run-shader-db.sh directly from the meson-main job. v2: * Also run prepare-artifacts.sh in meson-arm64 script v3: * Move tarball creation into the new script as well, as it prevented ccache --show-stats from running in after_script Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> # v1 Reviewed-by: Eric Anholt <eric@anholt.net>
2019-10-24 00:42:53 +08:00
- .gitlab-ci/run-shader-db.sh
gitlab-ci: Move up meson-main job definition In order to increase the chance of it running early. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-08-28 18:01:02 +08:00
ci: Add a release build with -Werror enabled. This will keep us from needing new MRs to fix up release build warnings after the fact. I've mostly derived from meson-gallium, dropping components that aren't clean yet. Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6462>
2020-08-25 01:15:35 +08:00
# Test a release build with -Werror so new warnings don't sneak in.
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-release:
ci: Add a release build with -Werror enabled. This will keep us from needing new MRs to fix up release build warnings after the fact. I've mostly derived from meson-gallium, dropping components that aren't clean yet. Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6462>
2020-08-25 01:15:35 +08:00
extends: .meson-build
variables:
UNWIND: "enabled"
DRI_LOADERS: >
-D glx=dri
-D gbm=enabled
-D egl=enabled
-D platforms=x11,wayland
GALLIUM_ST: >
-D dri3=enabled
-D gallium-extra-hud=true
-D gallium-vdpau=enabled
-D gallium-xvmc=disabled
-D gallium-omx=disabled
-D gallium-va=enabled
-D gallium-xa=enabled
-D gallium-nine=false
-D gallium-opencl=disabled
-D llvm=false
ci: Enable testing of i915g in the the debian -Werror release build. Acked-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11852>
2021-07-14 02:25:19 +08:00
GALLIUM_DRIVERS: "i915,iris,nouveau,kmsro,freedreno,r300,svga,swrast,v3d,vc4,virgl,etnaviv,panfrost,lima,zink,d3d12,crocus"
ci: enable building RADV in debian-release To build RADV without LLVM. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13117>
2021-09-30 19:39:24 +08:00
VULKAN_DRIVERS: "amd"
ci: Add a release build with -Werror enabled. This will keep us from needing new MRs to fix up release build warnings after the fact. I've mostly derived from meson-gallium, dropping components that aren't clean yet. Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6462>
2020-08-25 01:15:35 +08:00
BUILDTYPE: "release"
EXTRA_OPTION: >
ci: Make sure that osmesa stays warnings-clean in release builds. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1243>
2020-12-03 09:10:27 +08:00
-D osmesa=true
ci: Add a release build with -Werror enabled. This will keep us from needing new MRs to fix up release build warnings after the fact. I've mostly derived from meson-gallium, dropping components that aren't clean yet. Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6462>
2020-08-25 01:15:35 +08:00
-D tools=all
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
ci: Add a release build with -Werror enabled. This will keep us from needing new MRs to fix up release build warnings after the fact. I've mostly derived from meson-gallium, dropping components that aren't clean yet. Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6462>
2020-08-25 01:15:35 +08:00
ci: Add Fedora release build job The intention is for this to more or less match the Fedora package build. The main benefit right now is GCC 11 build test coverage. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-05-12 22:55:00 +08:00
fedora-release:
extends:
- .meson-build
- .use-fedora/x86_build
variables:
BUILDTYPE: "release"
C_ARGS: >
-Wno-error=array-bounds
-Wno-error=maybe-uninitialized
-Wno-error=stringop-overread
-Wno-error=uninitialized
CPP_ARGS: >
-Wno-error=array-bounds
DRI_LOADERS: >
-D glx=dri
-D gbm=enabled
-D egl=enabled
-D glvnd=true
-D platforms=x11,wayland
EXTRA_OPTION: >
-D osmesa=true
-D selinux=true
-D tools=drm-shim,etnaviv,freedreno,glsl,intel,nir,nouveau,lima,panfrost
GALLIUM_DRIVERS: "crocus,etnaviv,freedreno,iris,kmsro,lima,nouveau,panfrost,r300,r600,radeonsi,svga,swrast,tegra,v3d,vc4,virgl,zink"
GALLIUM_ST: >
-D dri3=enabled
-D gallium-extra-hud=true
-D gallium-vdpau=enabled
-D gallium-xvmc=disabled
-D gallium-omx=disabled
-D gallium-va=enabled
-D gallium-xa=enabled
-D gallium-nine=false
-D gallium-opencl=icd
-D gles1=disabled
-D gles2=enabled
-D llvm=enabled
-D microsoft-clc=disabled
-D shared-llvm=enabled
-D vulkan-device-select-layer=true
LLVM_VERSION: ""
UNWIND: "disabled"
VULKAN_DRIVERS: "amd,broadcom,freedreno,intel"
script:
- .gitlab-ci/meson/build.sh
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-android:
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
extends:
- .meson-cross
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/android_build
ci: Add a build test for the Android platform This builds the EGL loader and the freedreno, intel and amd vulkan drivers. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6112>
2020-07-29 06:35:36 +08:00
variables:
UNWIND: "disabled"
ci: Enable -Werror in clang jobs They're not warning-clean yet, but we can enable -Werror in general and just allow the existing types of warnings as exceptions with -Wno-error=[...]. This way, new warnings of all other types will be prevented from entering the code base. Once all warnings of a certain type have been eliminated in a job, the exception for that type can be dropped from that job. This provides a realistic path to a fully warning-clean CI build in the future. v2: * Use echo -n (Juan A. Suarez) Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10220>
2021-04-11 18:45:46 +08:00
C_ARGS: >
-Wno-error=absolute-value
-Wno-error=asm-operand-widths
-Wno-error=constant-conversion
-Wno-error=enum-conversion
-Wno-error=extern-initializer
-Wno-error=initializer-overrides
-Wno-error=missing-braces
-Wno-error=sometimes-uninitialized
-Wno-error=tautological-constant-out-of-range-compare
-Wno-error=unused-function
-Wno-error=unused-label
CPP_ARGS: >
-Wno-error=deprecated-declarations
-Wno-error=non-virtual-dtor
ci: Add a build test for the Android platform This builds the EGL loader and the freedreno, intel and amd vulkan drivers. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6112>
2020-07-29 06:35:36 +08:00
DRI_LOADERS: >
-D glx=disabled
-D gbm=disabled
-D egl=enabled
-D platforms=android
EXTRA_OPTION: >
-D android-stub=true
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
-D llvm=disabled
ci/android: Update to building for SDK 29 by default. This will get us build coverage of a bunch of Vulkan features, plus the ELF TLS support. Reviewed-by: Roman Stratiienko <r.stratiienko@gmail.com> Reviewed-by: Emil Velikov <emil.l.velikov@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10389>
2021-04-22 05:00:34 +08:00
-D platform-sdk-version=29
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: Add a build test for the Android platform This builds the EGL loader and the freedreno, intel and amd vulkan drivers. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6112>
2020-07-29 06:35:36 +08:00
GALLIUM_ST: >
-D dri3=disabled
-D gallium-vdpau=disabled
-D gallium-xvmc=disabled
-D gallium-omx=disabled
-D gallium-va=disabled
-D gallium-xa=disabled
-D gallium-nine=false
-D gallium-opencl=disabled
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
LLVM_VERSION: ""
ci/android: Make sure we don't detect system libexpat. There may be some more elegant way to do things, but the important thing is that android builds don't have any .pc files we should be using, other than what our CI generated for zlib. Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Jose Maria Casanova Crespo <jmcasanova@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9764>
2021-03-23 04:19:01 +08:00
PKG_CONFIG_LIBDIR: "/disable/non/android/system/pc/files"
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
script:
ci: enable venus in some meson build jobs Enable it in meson-{android,clang,vulkan,i386}. Signed-off-by: Chia-I Wu <olvaffe@gmail.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10124>
2021-04-09 12:01:58 +08:00
- PKG_CONFIG_PATH=/usr/local/lib/aarch64-linux-android/pkgconfig/:/android-ndk-r21d/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/aarch64-linux-android/pkgconfig/ CROSS=aarch64-linux-android GALLIUM_DRIVERS=etnaviv,freedreno,lima,panfrost,vc4,v3d VULKAN_DRIVERS=freedreno,broadcom,virtio-experimental .gitlab-ci/meson/build.sh
ci/android: Switch to using the Android NDK. To support Android drivers, we're going to want to be tracking that Mesa's build succeeds on a real android toolchain. This still uses the android stubs since these libs aren't in the NDK. Note that I had to drop the Intel and AMD drivers currently: we don't have LLVM cross-compiled for Android in this container, and I'm honestly hoping ACO saves us from that. Intel has dependencies on libexpat, which AOSP really doesn't want to bring in, and it looks to me like those dependencies could be optional. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6700>
2020-09-10 07:37:54 +08:00
# x86_64 build:
# Can't do Intel because gen_decoder.c currently requires libexpat, which
ci: Add RADV to Android CI. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13164>
2021-09-16 03:20:47 +08:00
# is not a dependency that AOSP wants to accept. Can't do Radeon Gallium
# drivers because they requires LLVM, which we don't have an Android build
# of.
- PKG_CONFIG_PATH=/usr/local/lib/x86_64-linux-android/pkgconfig/:/android-ndk-r21d/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/x86_64-linux-android/pkgconfig/ CROSS=x86_64-linux-android GALLIUM_DRIVERS=iris VULKAN_DRIVERS=amd,intel .gitlab-ci/meson/build.sh
ci: Add a build test for the Android platform This builds the EGL loader and the freedreno, intel and amd vulkan drivers. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6112>
2020-07-29 06:35:36 +08:00
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
.meson-cross:
extends:
- .meson-build
CI: Collapse SCons & meson-misc stages into one This is now called 'build-misc'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
stage: build-misc
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "disabled"
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
DRI_LOADERS: >
ci: build ARM mesa with X11 OpenGL support I want to run piglit with baremetal ci and for this opengl support is needed. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7370>
2020-10-17 20:00:45 +08:00
-D glx=dri
ci: build mesa with gbm We need gbm support for piglit. Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7370>
2020-10-27 05:01:07 +08:00
-D gbm=enabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D egl=enabled
ci: build ARM mesa with X11 OpenGL support I want to run piglit with baremetal ci and for this opengl support is needed. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7370>
2020-10-17 20:00:45 +08:00
-D platforms=x11
mesa: Retire classic OSMesa. The classic OSMesa renders directly into user memory using src/mesa/swrast, while gallium OSMesa renders using softpipe or llvmpipe and copies out at glFlush() time. This would make gallium look like a worse choice for OSMesa, except that swrast is: 1) Painfully slow to render compared to llvmpipe 2) Incorrect at derivatives 3) Limited to GL 2.1 instead of GL 4.6 In my survey of OSMesa users, debian was the remaining holdout with classic OSMesa in use on hurd and some rare non-LLVM-supported architectures (sh4, alpha, etc.). As of today, they've switched to softpipe-based gallium OSMesa for them. To prevent people from running the wrong OSMesa (to the extent that running OSMesa can ever be the right thing), delete the classic version. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Closes: #320 Closes: #877 Closes: #2297 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1243>
2019-07-04 02:10:32 +08:00
-D osmesa=false
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
GALLIUM_ST: >
ci: build ARM mesa with X11 OpenGL support I want to run piglit with baremetal ci and for this opengl support is needed. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7370>
2020-10-17 20:00:45 +08:00
-D dri3=enabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-vdpau=disabled
-D gallium-xvmc=disabled
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
-D gallium-omx=disabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-va=disabled
-D gallium-xa=disabled
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
-D gallium-nine=false
gitlab-ci: Use native aarch64 runner for ARM build jobs This allows running the regression tests. One downside is that we can't easily build the Vulkan overlay layer, because only x86 binaries of the glslang validator are available. If that's important, we could either use those binaries via qemu, or build it from source. v2: * Add :amd64 suffix to existing debian-9/10 job names (Eric Engestrom) Acked-by: Eric Engestrom <eric.engestrom@intel.com> # v1
2019-10-09 01:46:11 +08:00
.meson-arm:
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
extends:
- .meson-cross
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/arm_build
ci: Add "check mr" job to needs: of build jobs So that if the former fails, build & test jobs won't run, wasting less time & CI resources. This requires slight tweaks to the rules: of the former job, to make sure it always exists when the build jobs do. Acked-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7278>
2020-10-22 23:58:35 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/arm_build
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
variables:
gitlab-ci: add broadcom vulkan driver At this point we are only interested to test if it keeps building. v2: include meson-arm64 (Eric) Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6766>
2020-10-01 18:08:17 +08:00
VULKAN_DRIVERS: freedreno,broadcom
gitlab-ci: Enable llvmpipe in ARM build jobs v2: * Use LLVM 8 from buster-backports v3: * Use LLVM 7 again for armhf, llvmpipe is still broken there with LLVM 8 Acked-by: Eric Engestrom <eric.engestrom@intel.com>
2019-10-09 01:48:41 +08:00
GALLIUM_DRIVERS: "etnaviv,freedreno,kmsro,lima,nouveau,panfrost,swrast,tegra,v3d,vc4"
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
BUILDTYPE: "debugoptimized"
gitlab-ci: Use native aarch64 runner for ARM build jobs This allows running the regression tests. One downside is that we can't easily build the Vulkan overlay layer, because only x86 binaries of the glslang validator are available. If that's important, we could either use those binaries via qemu, or build it from source. v2: * Add :amd64 suffix to existing debian-9/10 job names (Eric Engestrom) Acked-by: Eric Engestrom <eric.engestrom@intel.com> # v1
2019-10-09 01:46:11 +08:00
tags:
- aarch64
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-armhf:
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:
- .meson-arm
- .ci-deqp-artifacts
gitlab-ci: Use native aarch64 runner for ARM build jobs This allows running the regression tests. One downside is that we can't easily build the Vulkan overlay layer, because only x86 binaries of the glslang validator are available. If that's important, we could either use those binaries via qemu, or build it from source. v2: * Add :amd64 suffix to existing debian-9/10 job names (Eric Engestrom) Acked-by: Eric Engestrom <eric.engestrom@intel.com> # v1
2019-10-09 01:46:11 +08:00
variables:
CROSS: armhf
ci: Remove LLVM from ARM test drivers. The LLVM libraries were a significant fraction of the entire payload (55M/250M uncompressed) into the initramfs of the test boards, but LLVM is only used for the draw module used in select/feedback (which isn't even tested in CI on ARM yet). Assume that llvmpipe draw is safe enough for ARM given the coverage on x86, and disable LLVM for these jobs. Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
2020-02-25 02:31:33 +08:00
EXTRA_OPTION: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D llvm=disabled
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: Allow better customization of the name of the artifacts for minio. To have asan testing, we need two different sets of artifacts per arch. Plus, "UPLOAD_FOR_LAVA" was misnamed at this point anyway. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2021-02-16 04:35:41 +08:00
MINIO_ARTIFACT_NAME: mesa-armhf
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
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.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
- .gitlab-ci/prepare-artifacts.sh
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-arm64:
gitlab-ci: Use native aarch64 runner for ARM build jobs This allows running the regression tests. One downside is that we can't easily build the Vulkan overlay layer, because only x86 binaries of the glslang validator are available. If that's important, we could either use those binaries via qemu, or build it from source. v2: * Add :amd64 suffix to existing debian-9/10 job names (Eric Engestrom) Acked-by: Eric Engestrom <eric.engestrom@intel.com> # v1
2019-10-09 01:46:11 +08:00
extends:
- .meson-arm
- .ci-deqp-artifacts
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
variables:
panvk/ci: Build-test panvk We still need to implement quite some functionality before it would make sense to run dEQP in CI, but it will be already useful to build-test it. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Acked-by: Boris Brezillon <boris.brezillon@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/12612>
2021-08-30 15:26:19 +08:00
VULKAN_DRIVERS: "freedreno,broadcom,panfrost"
ci: Remove LLVM from ARM test drivers. The LLVM libraries were a significant fraction of the entire payload (55M/250M uncompressed) into the initramfs of the test boards, but LLVM is only used for the draw module used in select/feedback (which isn't even tested in CI on ARM yet). Assume that llvmpipe draw is safe enough for ARM given the coverage on x86, and disable LLVM for these jobs. Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
2020-02-25 02:31:33 +08:00
EXTRA_OPTION: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D llvm=disabled
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci: Allow better customization of the name of the artifacts for minio. To have asan testing, we need two different sets of artifacts per arch. Plus, "UPLOAD_FOR_LAVA" was misnamed at this point anyway. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2021-02-16 04:35:41 +08:00
MINIO_ARTIFACT_NAME: mesa-arm64
gitlab-ci: Move artifact preparation to separate script It's currently only needed for the meson-main and meson-arm64 jobs, not the other meson build jobs. Also remove MESON_SHADERDB, just run .gitlab-ci/run-shader-db.sh directly from the meson-main job. v2: * Also run prepare-artifacts.sh in meson-arm64 script v3: * Move tarball creation into the new script as well, as it prevented ccache --show-stats from running in after_script Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> # v1 Reviewed-by: Eric Anholt <eric@anholt.net>
2019-10-24 00:42:53 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
gitlab-ci: Move artifact preparation to separate script It's currently only needed for the meson-main and meson-arm64 jobs, not the other meson build jobs. Also remove MESON_SHADERDB, just run .gitlab-ci/run-shader-db.sh directly from the meson-main job. v2: * Also run prepare-artifacts.sh in meson-arm64 script v3: * Move tarball creation into the new script as well, as it prevented ccache --show-stats from running in after_script Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> # v1 Reviewed-by: Eric Anholt <eric@anholt.net>
2019-10-24 00:42:53 +08:00
- .gitlab-ci/prepare-artifacts.sh
gitlab-ci: Move up meson-arm64 job definition This might allow the arm64 tests to start running earlier. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-09-13 17:59:43 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-arm64-asan:
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
extends:
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-arm64
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
variables:
ci: Enable -Werror for the remaining GCC build jobs Same principle as for clang, with much fewer exceptions left. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10220>
2021-04-11 18:50:36 +08:00
C_ARGS: >
-Wno-error=stringop-truncation
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
EXTRA_OPTION: >
-D llvm=disabled
-D b_sanitize=address
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
ARTIFACTS_DEBUG_SYMBOLS: 1
MINIO_ARTIFACT_NAME: mesa-arm64-asan
MESON_TEST_ARGS: "--no-suite mesa:compiler"
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-arm64-build-test:
ci: Split out radv build-testing on arm64 radv needs libllvm which increases our ramdisk size significantly. Since this driver is only build tested, we can split it out into a separate job. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
2020-02-20 23:37:48 +08:00
extends:
- .meson-arm
- .ci-deqp-artifacts
variables:
VULKAN_DRIVERS: "amd"
ci: Build-test Panfrost tools Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3348 Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Alyssa Rosenzweig <alyssa@rosenzweig.io> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6157>
2020-08-03 22:19:38 +08:00
EXTRA_OPTION: >
-Dtools=panfrost
ci: Split out radv build-testing on arm64 radv needs libllvm which increases our ramdisk size significantly. Since this driver is only build tested, we can split it out into a separate job. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
2020-02-20 23:37:48 +08:00
script:
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
ci: Split out radv build-testing on arm64 radv needs libllvm which increases our ramdisk size significantly. Since this driver is only build tested, we can split it out into a separate job. Signed-off-by: Rohan Garg <rohan.garg@collabora.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3928>
2020-02-20 23:37:48 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-clang:
gitlab-ci: List some longer-running jobs before others of the same stage This increases the chance of them running earlier, which can have an impact on the total duration of the pipeline. v2: * Minor style fix-up to moved comment (Eric Anholt) Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Acked-by: Eric Anholt <eric@anholt.net>
2019-03-20 22:58:31 +08:00
extends: .meson-build
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "enabled"
ci: Enable -Werror in clang jobs They're not warning-clean yet, but we can enable -Werror in general and just allow the existing types of warnings as exceptions with -Wno-error=[...]. This way, new warnings of all other types will be prevented from entering the code base. Once all warnings of a certain type have been eliminated in a job, the exception for that type can be dropped from that job. This provides a realistic path to a fully warning-clean CI build in the future. v2: * Use echo -n (Juan A. Suarez) Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10220>
2021-04-11 18:45:46 +08:00
C_ARGS: >
-Wno-error=constant-conversion
-Wno-error=enum-conversion
-Wno-error=implicit-const-int-float-conversion
-Wno-error=initializer-overrides
-Wno-error=sometimes-uninitialized
-Wno-error=unused-function
CPP_ARGS: >
-Wno-error=c99-designator
-Wno-error=deprecated-declarations
-Wno-error=implicit-const-int-float-conversion
-Wno-error=missing-braces
-Wno-error=overloaded-virtual
-Wno-error=tautological-constant-out-of-range-compare
-Wno-error=unused-const-variable
-Wno-error=unused-private-field
gitlab-ci: build GLVND in meson-clang Building GLVND in meson-main doesn't work because this disables libEGL and it's needed for running shader-db. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 21:37:32 +08:00
DRI_LOADERS: >
-D glvnd=true
ci: debian-clang: build more drivers Add gallium drivers: i915 + asahi Add vulkan drivers: swrast + panfrost These can now compile with the current no-error list Reviewed-by: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14289>
2021-12-22 18:28:46 +08:00
GALLIUM_DRIVERS: "iris,nouveau,kmsro,r300,r600,freedreno,swrast,svga,v3d,vc4,virgl,etnaviv,panfrost,lima,zink,radeonsi,tegra,d3d12,crocus,i915,asahi"
VULKAN_DRIVERS: intel,amd,freedreno,broadcom,virtio-experimental,swrast,panfrost
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
CC: clang
CXX: clang++
gitlab-ci: List some longer-running jobs before others of the same stage This increases the chance of them running earlier, which can have an impact on the total duration of the pipeline. v2: * Minor style fix-up to moved comment (Eric Anholt) Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Acked-by: Eric Anholt <eric@anholt.net>
2019-03-20 22:58:31 +08:00
Revert "CI: Disable Windows jobs" They're fixed now, just in time. This reverts commit 7b44e7d7bb77051913ce24ea177d06820c40304c. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13708>
2021-11-08 21:08:48 +08:00
windows-vs2019:
gitlab-ci: Add a job for meson on windows This adds a new CI job that runs on windows with MSVC. It currently builds softpipe and osmesa, and runs the related unit tests. It does rely on meson's wraps for zlib, but I've set up caching of the wrap dependencies so hopefully that wont be a problem. I really wanted to user powershell for this, but there just isn't an easy way to do that, it's much easier to use batch scripts, so thats what I used. The leading `/` for .gitlab-ci/lava... must be removed because windows doesn't understand it, and when it reads the file the job ends in error. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:36:19 +08:00
extends:
- .build-windows
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
- .use-windows_build_vs2019
CI: Add Windows source dependency map Now that we've soaked the Windows build in and it's working well, restrict it to only running on given pipelines, albeit in a somewhat surprising way. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8053>
2020-12-11 18:41:32 +08:00
- .windows-build-rules
CI: Collapse SCons & meson-misc stages into one This is now called 'build-misc'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
stage: build-misc
gitlab-ci: Add a job for meson on windows This adds a new CI job that runs on windows with MSVC. It currently builds softpipe and osmesa, and runs the related unit tests. It does rely on meson's wraps for zlib, but I've set up caching of the wrap dependencies so hopefully that wont be a problem. I really wanted to user powershell for this, but there just isn't an easy way to do that, it's much easier to use batch scripts, so thats what I used. The leading `/` for .gitlab-ci/lava... must be removed because windows doesn't understand it, and when it reads the file the job ends in error. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:36:19 +08:00
script:
CI: Add native Windows VS2019 build Adds a native build of Mesa using Meson with the Visual Studio 2019 toolchain on a Windows host. Though Docker is supported on Windows, Docker-in-Docker is not possible, nor are podman and skopeo available. We handle this by creating the container from a shell-executor Windows machine, which gives us a native PowerShell that we can execute Docker from. This attempts to do the same copy-from-upstream-or-create-if-not-exists optimisation as the ci-templates do for our Linux builds, albeit open-coded in PowerShell. The Mesa build itself is executed inside a container, using Meson and Ninja. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Acked-by: Jose Fonseca <jfonseca@vmware.com> Acked-by: Brian Paul <brianp@vmware.com> Acked-by: Eric Engestrom <eric@engestrom.ch> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4304>
2020-03-24 19:11:36 +08:00
- . .\.gitlab-ci\windows\mesa_build.ps1
gitlab-ci: store build-artifacts from building mesa GitLab CI doesn't allow us to store artifacts from outside the build-directory, so let's create an install-directory and install there instead. To do this properly, we need to expand a variable inside the command-line, so we need to change to a double-quoted string. Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7857>
2020-06-05 04:55:52 +08:00
artifacts:
paths:
ci/windows: Artifact Meson build and test logs These are useful, especially when tests fail. The other jobs do this, so fall into line. Signed-off-by: Daniel Stone <daniels@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11261>
2021-06-09 19:39:32 +08:00
- _build/meson-logs/*.txt
gitlab-ci: store build-artifacts from building mesa GitLab CI doesn't allow us to store artifacts from outside the build-directory, so let's create an install-directory and install there instead. To do this properly, we need to expand a variable inside the command-line, so we need to change to a double-quoted string. Reviewed-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7857>
2020-06-05 04:55:52 +08:00
- _install/
gitlab-ci: Add a job for meson on windows This adds a new CI job that runs on windows with MSVC. It currently builds softpipe and osmesa, and runs the related unit tests. It does rely on meson's wraps for zlib, but I've set up caching of the wrap dependencies so hopefully that wont be a problem. I really wanted to user powershell for this, but there just isn't an easy way to do that, it's much easier to use batch scripts, so thats what I used. The leading `/` for .gitlab-ci/lava... must be removed because windows doesn't understand it, and when it reads the file the job ends in error. Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2019-10-24 05:36:19 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-clover:
gitlab-ci: add meson gallium ST Clover (LLVM 5.0) build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-29 02:05:22 +08:00
extends: .meson-build
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "enabled"
gitlab-ci: add meson gallium ST Clover (LLVM 5.0) build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-29 02:05:22 +08:00
DRI_LOADERS: >
-D glx=disabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D egl=disabled
-D gbm=disabled
gitlab-ci: Move LLVM/clang 6/7 packages to the x86_build_old image They're available in Debian 9 (stretch) as well. This will avoid conflicts with packages from Debian testing. Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-05-31 05:55:28 +08:00
GALLIUM_DRIVERS: "r600,radeonsi"
gitlab-ci: add meson gallium ST Clover (LLVM 5.0) build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-29 02:05:22 +08:00
GALLIUM_ST: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D dri3=disabled
-D gallium-vdpau=disabled
-D gallium-xvmc=disabled
gitlab-ci: add meson gallium ST Clover (LLVM 5.0) build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-29 02:05:22 +08:00
-D gallium-omx=disabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-va=disabled
-D gallium-xa=disabled
gitlab-ci: add meson gallium ST Clover (LLVM 5.0) build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com>
2019-01-29 02:05:22 +08:00
-D gallium-nine=false
-D gallium-opencl=icd
ci: Enable -Werror in more clover builds. We've slowly been pushing -Werror through the set of CI builds, and it looks like clover is clean at the moment. Keep it that way. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Rob Clark <robdclark@chromium.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7664>
2020-11-18 04:06:53 +08:00
EXTRA_OPTION: >
ci: Disable valgrind in some build jobs Once the glcpp valgrind test works as intended again, it would delay the dependent test jobs by ~1-4 minutes. The meson-clover job would run the glcpp valgrind test multiple times and take more than 10 minutes to finish. valgrind can't work in the meson-android job, would need an ARM backend. v2: * Disable in meson-clover as well. Reviewed-by: Dylan Baker <dylan.c.baker@intel.com> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9528>
2021-03-12 01:17:52 +08:00
-D valgrind=false
gitlab-ci: Build clover against all supported versions of LLVM And consolidate it all into a single job. It doesn't take much longer than a single version, thanks to ccache. Overall, this single job might be faster or at least use fewer CPU cycles than the two jobs before, while covering thrice as many versions of LLVM. v2: * Move "rm -rf _build" to meson-build.sh. * Set GALLIUM_DRIVERS the same way both times in the meson-clover job, for symmetry. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> # v1
2019-05-03 16:58:48 +08:00
script:
ci: don't build clover with LLVM 9 on radeonsi because it's unsupported Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10199>
2021-04-15 03:46:15 +08:00
- LLVM_VERSION=9 GALLIUM_DRIVERS=r600,swrast .gitlab-ci/meson/build.sh
ci: Move meson-build.sh to meson/build.sh A little less clutter in the top .gitlab-ci directory. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9472>
2021-03-09 01:11:27 +08:00
- .gitlab-ci/meson/build.sh
gitlab-ci: Create separate docker images for Debian stretch & buster Pros: * Less fragile due to not mixing packages from stretch and buster * No longer need to use third-party LLVM packages * The buster image now uses GCC 8 for C++ as well (previously 6 for C++, 8 for C), allowing to drop some hacks Con: * The stretch image now only uses GCC 6 for C as well as C++ * Need separate jobs for testing old LLVM versions Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-09-06 23:04:47 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-vulkan:
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
extends: .meson-build
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "disabled"
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
DRI_LOADERS: >
-D glx=disabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gbm=disabled
-D egl=disabled
egl: automatically compile the `drm` platform when available Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Emil Velikov <emil.velikov@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3161>
2019-06-25 22:44:16 +08:00
-D platforms=x11,wayland
mesa: Retire classic OSMesa. The classic OSMesa renders directly into user memory using src/mesa/swrast, while gallium OSMesa renders using softpipe or llvmpipe and copies out at glFlush() time. This would make gallium look like a worse choice for OSMesa, except that swrast is: 1) Painfully slow to render compared to llvmpipe 2) Incorrect at derivatives 3) Limited to GL 2.1 instead of GL 4.6 In my survey of OSMesa users, debian was the remaining holdout with classic OSMesa in use on hurd and some rare non-LLVM-supported architectures (sh4, alpha, etc.). As of today, they've switched to softpipe-based gallium OSMesa for them. To prevent people from running the wrong OSMesa (to the extent that running OSMesa can ever be the right thing), delete the classic version. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Closes: #320 Closes: #877 Closes: #2297 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1243>
2019-07-04 02:10:32 +08:00
-D osmesa=false
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
GALLIUM_ST: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D dri3=enabled
-D gallium-vdpau=disabled
-D gallium-xvmc=disabled
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
-D gallium-omx=disabled
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-D gallium-va=disabled
-D gallium-xa=disabled
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
-D gallium-nine=false
-D gallium-opencl=disabled
gitlab-ci: Enable UBSan for the meson-vulkan job It doesn't report any errors now. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Adam Jackson <ajax@redhat.com>
2019-09-25 18:56:58 +08:00
-D b_sanitize=undefined
-D c_args=-fno-sanitize-recover=all
-D cpp_args=-fno-sanitize-recover=all
UBSAN_OPTIONS: "print_stacktrace=1"
ci: enable venus in some meson build jobs Enable it in meson-{android,clang,vulkan,i386}. Signed-off-by: Chia-I Wu <olvaffe@gmail.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10124>
2021-04-09 12:01:58 +08:00
VULKAN_DRIVERS: intel,amd,freedreno,broadcom,virtio-experimental
gitlab-ci: add the vulkan overlay layer to the vulkan build Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
2019-05-09 00:17:23 +08:00
EXTRA_OPTION: >
gitlab-ci: fix vulkan build layer enabling Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Fixes: 54fe5b0482df0f ("meson: switch vulkan layer to list of choices") Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9858>
2021-03-26 22:50:08 +08:00
-D vulkan-layers=device-select,overlay
ci: enable ACO tests Signed-off-by: Rhys Perry <pendingchaos02@gmail.com> Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Acked-by: Daniel Schürmann <daniel@schuermann.dev> Acked-by: Timur Kristóf <timur.kristof@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3521>
2020-06-03 21:25:12 +08:00
-D build-aco-tests=true
gitlab-ci: Reorder jobs a bit to be generally ordered longer => shorter This makes the longer jobs likely to run earlier, which can help the overall pipeline duration. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-05-04 00:19:25 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-i386:
gitlab-ci: Use separate docker images for cross builds Using x86_build-base as a separate base layer as well for storage & network bandwidth efficiency. Using separate images allows dropping the workarounds from the cross build job scripts. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5296>
2020-06-02 01:08:30 +08:00
extends:
- .meson-cross
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/i386_build
gitlab-ci: Build i386 and ARM drivers in surfaceless mode. I don't particularly care about getting x86/ARM cross-build coverage of all the window systems, but we do want to be building src/mesa/ (for x86 asm) and gallium drivers (for vc4 NEON asm). I'm also hoping to use these build products for testing freedreno on actual HW (which we do using surfaceless). This increases the docker image from 1.4G to 1.5G. Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Acked-by: Eric Engestrom <eric@engestrom.ch>
2019-07-12 03:58:28 +08:00
variables:
gitlab-ci: simplify $CROSS option Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
2019-08-10 06:46:50 +08:00
CROSS: i386
ci: enable venus in some meson build jobs Enable it in meson-{android,clang,vulkan,i386}. Signed-off-by: Chia-I Wu <olvaffe@gmail.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10124>
2021-04-09 12:01:58 +08:00
VULKAN_DRIVERS: intel,amd,swrast,virtio-experimental
ci: add crocus to the build tests Reviewed-by: Jason Ekstrand <jason@jlekstrand.net> Acked-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11146>
2021-06-03 03:52:40 +08:00
GALLIUM_DRIVERS: "iris,nouveau,r300,r600,radeonsi,swrast,virgl,zink,crocus"
gitlab-ci: Build i386 and ARM drivers in surfaceless mode. I don't particularly care about getting x86/ARM cross-build coverage of all the window systems, but we do want to be building src/mesa/ (for x86 asm) and gallium drivers (for vc4 NEON asm). I'm also hoping to use these build products for testing freedreno on actual HW (which we do using surfaceless). This increases the docker image from 1.4G to 1.5G. Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Acked-by: Eric Engestrom <eric@engestrom.ch>
2019-07-12 03:58:28 +08:00
EXTRA_OPTION: >
gitlab-ci: fix vulkan build layer enabling Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com> Fixes: 54fe5b0482df0f ("meson: switch vulkan layer to list of choices") Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9858>
2021-03-26 22:50:08 +08:00
-D vulkan-layers=device-select,overlay
gitlab-ci: Build i386 and ARM drivers in surfaceless mode. I don't particularly care about getting x86/ARM cross-build coverage of all the window systems, but we do want to be building src/mesa/ (for x86 asm) and gallium drivers (for vc4 NEON asm). I'm also hoping to use these build products for testing freedreno on actual HW (which we do using surfaceless). This increases the docker image from 1.4G to 1.5G. Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Acked-by: Eric Engestrom <eric@engestrom.ch>
2019-07-12 03:58:28 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-s390x:
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
extends:
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-ppc64el
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/s390x_build
ci: Condition s390x on specific drivers Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10926>
2021-05-21 23:25:55 +08:00
- .s390x-rules
gitlab-ci: Restrict s390x/ppc64el jobs to packet runners They are hitting timeouts on the gstreamer runners now... *sigh* Reviewed-by: Adam Jackson <ajax@redhat.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4233> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4233>
2020-03-19 01:41:43 +08:00
tags:
- kvm
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
variables:
CROSS: s390x
ci: Add a few more drivers to the cross builds This is mostly to get additional -Werror coverage to avoid introducing unforced ILP32 or big-endian errors. i386 adds lavapipe, r600, nouveau, zink, and all the classic drivers. ppc64le adds lavapipe and zink, and also adds -Werror for symmetry with the other cross builds. s390x also adds lavapipe and zink. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8394>
2021-01-08 23:10:53 +08:00
GALLIUM_DRIVERS: "swrast,zink"
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
# The lp_test_blend test times out with LLVM 11
LLVM_VERSION: 9
ci: Add a few more drivers to the cross builds This is mostly to get additional -Werror coverage to avoid introducing unforced ILP32 or big-endian errors. i386 adds lavapipe, r600, nouveau, zink, and all the classic drivers. ppc64le adds lavapipe and zink, and also adds -Werror for symmetry with the other cross builds. s390x also adds lavapipe and zink. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8394>
2021-01-08 23:10:53 +08:00
VULKAN_DRIVERS: "swrast"
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-ppc64el:
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
extends:
ci: Move docker images from Debian buster to bullseye Among other things, this gets us GCC 10 (was 6). Requires some changes to third party components we use: * Install apitrace (& waffle) from Debian; was hitting issues with the local build, and it's the same version 9.0 anyway. * Update Fossilize to a newer commit which builds with GCC 10. * apt.llvm.org repositories are no longer needed. * Use an SPIRV-LLVM-Translator commit which builds with LLVM 11.0.1. * Install XCB packages from Debian, 1.13 fails to build with Python 3.9. * Install wayland-protocols from Debian, 1.12 is too old for libgtk-3-dev in bullseye. LLVM 7/8 packages are no longer available. Also adapt expected test results to Xvfb now exposing multi-samle GLXFBConfigs. v2: * Install clang instead of clang-11. Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3124 Reviewed-by: Eric Anholt <eric@anholt.net> # v1 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9833>
2021-03-19 19:52:35 +08:00
- .meson-cross
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/ppc64el_build
ci: Condition ppc64-el on specific drivers Changes to Panfrost or Freedreno should not trigger ppc64 rebuilds. Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10926>
2021-05-21 23:24:17 +08:00
- .ppc64el-rules
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
variables:
CROSS: ppc64el
ci: Add a few more drivers to the cross builds This is mostly to get additional -Werror coverage to avoid introducing unforced ILP32 or big-endian errors. i386 adds lavapipe, r600, nouveau, zink, and all the classic drivers. ppc64le adds lavapipe and zink, and also adds -Werror for symmetry with the other cross builds. s390x also adds lavapipe and zink. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8394>
2021-01-08 23:10:53 +08:00
GALLIUM_DRIVERS: "nouveau,radeonsi,swrast,virgl,zink"
VULKAN_DRIVERS: "amd,swrast"
gitlab-ci: Add ppc64el and s390x cross-build jobs Using LLVM 8 for ppc64el and 7 for s390x (which hits some coroutine related issues with LLVM 8). There are some test failures we need to ignore for now. Also, the timeout needs to be bumped from the default 30s for some tests, because they can take longer under emulation. Reviewed-by: Adam Jackson <ajax@redhat.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3643>
2020-01-31 01:21:15 +08:00
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
debian-mingw32-x86_64:
gitlab-ci: Add a mingw x86_64 job Acked-by: Eric Engestrom <eric.engestrom@intel.com> (v1) Acked-by: Kristian H. Kristensen <hoegsberg@google.com>
2019-09-20 01:21:51 +08:00
extends: .meson-build
CI: Collapse SCons & meson-misc stages into one This is now called 'build-misc'. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com> Acked-by: Eric Anholt <eric@anholt.net> Acked-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7873>
2020-12-02 21:50:38 +08:00
stage: build-misc
gitlab-ci: Add a mingw x86_64 job Acked-by: Eric Engestrom <eric.engestrom@intel.com> (v1) Acked-by: Kristian H. Kristensen <hoegsberg@google.com>
2019-09-20 01:21:51 +08:00
variables:
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
UNWIND: "disabled"
ci: Enable -Werror for the remaining GCC build jobs Same principle as for clang, with much fewer exceptions left. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10220>
2021-04-11 18:50:36 +08:00
C_ARGS: >
-Wno-error=format
-Wno-error=format-extra-args
CPP_ARGS: $C_ARGS
gitlab-ci: Add a mingw x86_64 job Acked-by: Eric Engestrom <eric.engestrom@intel.com> (v1) Acked-by: Kristian H. Kristensen <hoegsberg@google.com>
2019-09-20 01:21:51 +08:00
GALLIUM_DRIVERS: "swrast"
EXTRA_OPTION: >
meson: deprecated 'true' and 'false' in combo options for 'enabled' and 'disabled' To prepare to use meson's builtin feature options in the future, which are more powerful and provide useful feature for packagers, like the ability to turn all "automagic" features off, and then explicitly turn on the ones they want. This is designed to make the transition softer, since the 'true' and 'false' are still accepted, just with a warning. Acked-by: Matt Turner <mattst88@gmail.com> Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4740>
2020-05-20 05:01:47 +08:00
-Dllvm=disabled
gitlab-ci: Build meson-mingw32-x86_64 w/o zlib. To prevent hard requirement of zlib from creeping in, as https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9689 Reviewed-by: Jesse Natalie <jenatali@microsoft.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9727>
2021-03-20 18:41:25 +08:00
-Dzlib=disabled
mesa: Retire classic OSMesa. The classic OSMesa renders directly into user memory using src/mesa/swrast, while gallium OSMesa renders using softpipe or llvmpipe and copies out at glFlush() time. This would make gallium look like a worse choice for OSMesa, except that swrast is: 1) Painfully slow to render compared to llvmpipe 2) Incorrect at derivatives 3) Limited to GL 2.1 instead of GL 4.6 In my survey of OSMesa users, debian was the remaining holdout with classic OSMesa in use on hurd and some rare non-LLVM-supported architectures (sh4, alpha, etc.). As of today, they've switched to softpipe-based gallium OSMesa for them. To prevent people from running the wrong OSMesa (to the extent that running OSMesa can ever be the right thing), delete the classic version. Reviewed-by: Eric Engestrom <eric.engestrom@intel.com> Closes: #320 Closes: #877 Closes: #2297 Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/1243>
2019-07-04 02:10:32 +08:00
-Dosmesa=true
gitlab-ci: Add a mingw x86_64 job Acked-by: Eric Engestrom <eric.engestrom@intel.com> (v1) Acked-by: Kristian H. Kristensen <hoegsberg@google.com>
2019-09-20 01:21:51 +08:00
--cross-file=.gitlab-ci/x86_64-w64-mingw32
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
.test:
gitlab-ci: set a common job parent for test stage Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:53:15 +08:00
extends:
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
- .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: set a common job parent for test stage Signed-off-by: Eric Engestrom <eric.engestrom@intel.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-10-15 06:53:15 +08:00
variables:
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
GIT_STRATEGY: none # testing doesn't build anything from source
before_script:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
- !reference [default, before_script]
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +08:00
# Note: Build dir (and thus install) may be dirty due to GIT_STRATEGY
- rm -rf install
- tar -xf artifacts/install.tar
gitlab-ci: fix ldd check for Vulkan drivers The 'dri' directory isn't created when building Vulkan drivers. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-14 21:00:46 +08:00
- LD_LIBRARY_PATH=install/lib find install/lib -name "*.so" -print -exec ldd {} \;
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +08:00
artifacts:
gitlab-ci/deqp: detect and report flakes If there are a small number of fails, re-run to determine if they are flakes, and optionally (if `$FLAKES_CHANNEL` configured) report the flakes. This way flakes don't interfere with developers working on other drivers, but get logged so that the developers working on the flaking driver can monitor the situation. Signed-off-by: Rob Clark <robdclark@chromium.org> Acked-by: Eric Engestrom <eric.engestrom@intel.com>
2019-11-18 03:33:01 +08:00
when: always
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}"
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +08:00
paths:
- results/
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
.use-debian/x86_test-gl:
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
extends:
- .test
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_test-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/x86_test-gl"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-x86_test-gl
gitlab-ci: Explicitly list debian-10 in needs: for .deqp-test template Apparently needs: in a definition overwrites inherited ones. So .deqp-test effectively didn't declare needs: for debian-10, which means any jobs based on .deqp-test could spuriously run after the debian-10 job failed or was cancelled.
2019-10-22 17:19:17 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_test-gl
gitlab-ci: Run the GLES2 CTS on llvmpipe. This is the start of doing CTS tests on merges to Mesa master. We use the surfaceless platform so that we don't need to bother bringing up weston or X11. The surface size is kept low to reduce runtime, but this comes at the cost of many rendering tests skipping due to too-small render targets (as we see the impact of Mesa on the shared runner pool, we can reevaluate this and what set of CTS tests we want to run). We split the job up across 4 runners (each at 4 llvmpipe threads), so that the job can load-balance across our shared runners and finish sooner (since dEQP is very single-thread-performance bound). Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>
2019-06-29 07:35:32 +08:00
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
.test-gl:
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_test-gl
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_test-gl
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-testing
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
.test-vk:
extends:
- .test
ci: Incorporate base image tag into dependent image tags Using new .incorporate-base-tag+templates-commit & .set-image-base-tag templates. This automatically ensures dependent images get rebuilt along with the base image, no more need to manually bump the dependent image tags. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-12 02:00:40 +08:00
- .set-image-base-tag
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
variables:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_BASE_TAG: *debian-x86_test-base
ci: Add and use .set-image template to construct docker image name Instead of open-coding everywhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7988>
2020-12-10 01:58:48 +08:00
MESA_IMAGE_PATH: "debian/x86_test-vk"
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
MESA_IMAGE_TAG: *debian-x86_test-vk
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
needs:
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-testing
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_test-vk
gitlab-ci: add a new base test job for VK Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-18 16:30:27 +08:00
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
.test-cl:
extends:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- .use-debian/x86_test-gl
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/x86_test-gl
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- debian-clover-testing
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
ci: add VKD3D-Proton testsuite runner 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/10870>
2021-05-18 21:54:54 +08:00
.vkd3d-proton-test:
artifacts:
when: on_failure
name: "mesa_${CI_JOB_NAME}"
paths:
- results/vkd3d-proton.log
script:
ci: fix the vkd3d-proton runner 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/11087>
2021-06-01 03:35:25 +08:00
- ./install/vkd3d-proton/run.sh
ci: add VKD3D-Proton testsuite runner 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/10870>
2021-05-18 21:54:54 +08:00
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
.piglit-test:
gitlab-ci: Put HTML summary in artifacts for failed piglit jobs This will make it easier to look at details of failed / skipped tests. Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-11-26 01:42:10 +08:00
artifacts:
when: on_failure
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}"
gitlab-ci: Put HTML summary in artifacts for failed piglit jobs This will make it easier to look at details of failed / skipped tests. Acked-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net>
2019-11-26 01:42:10 +08:00
paths:
ci: correct piglit's HTML summary location for artifacts upload Signed-off-by: Andres Gomez <agomez@igalia.com> Acked-by: Eric Anholt <eric@anholt.net> Reviewed-by: Juan A. Suarez <jasuarez@igalia.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9092>
2021-02-17 06:28:02 +08:00
- results/summary/
ci/piglit: Include the updated piglit results list in the job results. If you're standing up a new piglit CI, you're going to want it. Reviewed-by: Adam Jackson <ajax@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8068>
2020-12-12 02:40:57 +08:00
- results/*.txt
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:
PIGLIT_NO_WINDOW: 1
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
CI_JOB_JWT_FILE: /minio_jwt # JWT file on piglit jobs should be available on / partition
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
script:
gitlab-ci: Place files from the Mesa repo into the build tarball There's some files from the .gitlab-ci directory that are needed in the test stage and that, because the Mesa repository isn't checked out in that stage, need to be made available through other means. Because those files are going to be needed in LAVA devices, place them ino the tarball containing the built files so it's available to both gitlab-ci runners and LAVA devices. Before those files were passed in the artifacts of the Gitlab CI job, but this commit places them into the built tarball so scripts later in the pipeline don't need to account for this discrepancy. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
2020-03-24 19:58:30 +08:00
- install/piglit/run.sh
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
ci: add piglit replay jobs and remove tracie ones Along the way, modify the piglit run script and refactor the way piglit jobs are generated. v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Extend information in the comments about the need to use a running X server for replaying with Vulkan (Tomeu). - Do actually fail if the upload doesn't work (Tomeu). v4: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v3] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-19 21:42:56 +08:00
.piglit-traces-test:
ci: enable piglit testing of clover/llvmpipe. This adds support for building clover/llvmpipe and running the piglit CL tests on it. It uses the gl testing container, and add builds the libclc spirv libraries as part of that which requires the llvm spirv translator in the build container. It also builds the llvm spirv translator as part of the build root and creates a mesa build that builds clover for testing against it. It uses llvm 10 as the baseline. This drops bswap as it has an oob memory access with llvmpipe which cause flaky test results. phatk also seems flaky Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6901>
2020-09-29 06:40:13 +08:00
extends:
- .piglit-test
ci: add piglit replay jobs and remove tracie ones Along the way, modify the piglit run script and refactor the way piglit jobs are generated. v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Extend information in the comments about the need to use a running X server for replaying with Vulkan (Tomeu). - Do actually fail if the upload doesn't work (Tomeu). v4: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v3] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-19 21:42:56 +08:00
cache:
key: ${CI_JOB_NAME}
paths:
- replayer-db/
artifacts:
when: on_failure
name: "mesa_${CI_JOB_NAME}"
reports:
junit: results/junit.xml
variables:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
CI_JOB_JWT_FILE: /minio_jwt # JWT file on piglit jobs should be available on / partition
ci: add piglit replay jobs and remove tracie ones Along the way, modify the piglit run script and refactor the way piglit jobs are generated. v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Extend information in the comments about the need to use a running X server for replaying with Vulkan (Tomeu). - Do actually fail if the upload doesn't work (Tomeu). v4: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v3] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-19 21:42:56 +08:00
PIGLIT_PROFILES: replay
PIGLIT_REPLAY_UPLOAD_TO_MINIO: 1
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
PIGLIT_REPLAY_EXTRA_ARGS: --keep-image --db-path ${CI_PROJECT_DIR}/replayer-db/ --minio_host=minio-packet.freedesktop.org --minio_bucket=mesa-tracie-public --role-session-name=${CI_PROJECT_PATH}:${CI_JOB_ID} --jwt-file=${CI_JOB_JWT_FILE}
ci: add piglit replay jobs and remove tracie ones Along the way, modify the piglit run script and refactor the way piglit jobs are generated. v2: - Squashed the commit to remove tracie jobs (Eric). v3: - Extend information in the comments about the need to use a running X server for replaying with Vulkan (Tomeu). - Do actually fail if the upload doesn't work (Tomeu). v4: - Rename *-piglit-traces jobs with *-traces. Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> [v3] Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-08-19 21:42:56 +08:00
PIGLIT_JUNIT_RESULTS: 1
gitlab-ci: allow to run dEQP Vulkan with DEQP_VER Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 15:39:00 +08:00
.deqp-test:
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
script:
gitlab-ci: Place files from the Mesa repo into the build tarball There's some files from the .gitlab-ci directory that are needed in the test stage and that, because the Mesa repository isn't checked out in that stage, need to be made available through other means. Because those files are going to be needed in LAVA devices, place them ino the tarball containing the built files so it's available to both gitlab-ci runners and LAVA devices. Before those files were passed in the artifacts of the Gitlab CI job, but this commit places them into the built tarball so scripts later in the pipeline don't need to account for this discrepancy. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
2020-03-24 19:58:30 +08:00
- ./install/deqp-runner.sh
ci/deqp: Upgrade the runner, enable junit output. I moved QPA-to-XML conversion to the runner, so Mesa CI (and developers!) don't need to do quite so much in bash. I also made it clean up caselist .qpa files since nobody ever wants them and we deleted them anyway. This cleans up a ton of the job log output. Additionally, I added a subcommend to turn the .csv into a junit output that we can expose to gitlab. Now, the pipeline's status page will report the failed testcases, and the "detail" button will give you a link to the .XML to view for the failure. (We don't report all testcases because it's too much load for the gitlab server). Note that this will 404 for the LAVA runners for now, as they don't retain artifacts in gitlab (the plan is to eventually have them minio upload the artifacts). This uprev also includes a deqp output parsing fix, resulting in us catching a couple more failures in some drivers. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8206>
2020-12-19 08:47:51 +08:00
artifacts:
ci/lavapipe: Don't include deqp's shader_cache in the artifacts. We don't care to look at it and we don't reuse it. Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10297>
2021-02-06 06:46:48 +08:00
exclude:
- results/*.shader_cache
ci/deqp: Upgrade the runner, enable junit output. I moved QPA-to-XML conversion to the runner, so Mesa CI (and developers!) don't need to do quite so much in bash. I also made it clean up caselist .qpa files since nobody ever wants them and we deleted them anyway. This cleans up a ton of the job log output. Additionally, I added a subcommend to turn the .csv into a junit output that we can expose to gitlab. Now, the pipeline's status page will report the failed testcases, and the "detail" button will give you a link to the .XML to view for the failure. (We don't report all testcases because it's too much load for the gitlab server). Note that this will 404 for the LAVA runners for now, as they don't retain artifacts in gitlab (the plan is to eventually have them minio upload the artifacts). This uprev also includes a deqp output parsing fix, resulting in us catching a couple more failures in some drivers. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8206>
2020-12-19 08:47:51 +08:00
reports:
junit: results/junit.xml
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
gitlab-ci: allow to run dEQP Vulkan with DEQP_VER Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
2019-11-19 15:39:00 +08:00
.deqp-test-vk:
extends:
- .deqp-test
variables:
DEQP_VER: vk
gitlab-ci: add Fossilize support to detect compiler regressions Fossilize is equivalent to vkpipeline-db but it's definitely more robust. This is based on the CI traces system. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
2020-02-26 16:33:14 +08:00
.fossilize-test:
script:
gitlab-ci: Place files from the Mesa repo into the build tarball There's some files from the .gitlab-ci directory that are needed in the test stage and that, because the Mesa repository isn't checked out in that stage, need to be made available through other means. Because those files are going to be needed in LAVA devices, place them ino the tarball containing the built files so it's available to both gitlab-ci runners and LAVA devices. Before those files were passed in the artifacts of the Gitlab CI job, but this commit places them into the built tarball so scripts later in the pipeline don't need to account for this discrepancy. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4295>
2020-03-24 19:58:30 +08:00
- ./install/fossilize-runner.sh
gitlab-ci: attach the Fossilize log file as artifact on failure It might be help. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5627>
2020-06-25 17:21:12 +08:00
artifacts:
when: on_failure
name: "mesa_${CI_JOB_NAME}"
paths:
- results/
gitlab-ci: add Fossilize support to detect compiler regressions Fossilize is equivalent to vkpipeline-db but it's definitely more robust. This is based on the CI traces system. Signed-off-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Reviewed-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/3960>
2020-02-26 16:33:14 +08:00
ci: Move db820c and db410c's gles3 tests to manual, like radv did. This should make these tests available for clicking on the web ui in personal branches, while hiding them from marge and the post-merge CI pipelines. We had already disabled db410c's gles3, but it wasn't available in the ui and you had to hack .gitalb-ci.yml. db820c is now being disabled by default, due to instaboots mentioned in https://gitlab.freedesktop.org/mesa/mesa/issues/2649 Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247>
2020-03-20 02:45:01 +08:00
# Rules for tests that should not be present in MRs or the main
# project's pipeline (don't block marge or report red on
.gitlab-ci.yml: Use main branch for gitlab ci Reworks: * Fix mesa/mesamaster typo to mesa/mesa main (anholt) * Use $CI_DEFAULT_BRANCH (eric_engestrom) Signed-off-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Eric Anholt <eric@anholt.net> Reviewed-by: Eric Engestrom <eric@engestrom.ch>
2021-04-27 04:16:55 +08:00
# mesa/mesa main) but should be present on pipelines in personal
ci: Move db820c and db410c's gles3 tests to manual, like radv did. This should make these tests available for clicking on the web ui in personal branches, while hiding them from marge and the post-merge CI pipelines. We had already disabled db410c's gles3, but it wasn't available in the ui and you had to hack .gitalb-ci.yml. db820c is now being disabled by default, due to instaboots mentioned in https://gitlab.freedesktop.org/mesa/mesa/issues/2649 Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247>
2020-03-20 02:45:01 +08:00
# branches (so you can opt in to running the flaky test when you want
# to).
.test-manual:
rules:
gitlab-ci: do not run full CI on scheduled pipelines Currently, scheduled pipelines are only used to rebuild the git-cache archive daily. There is no point in rebuilding eveything, so ensure that any normal jobs are removed from the scheduled pipelines. Reviewed-by: Michel Dänzer <mdaenzer@redhat.com> Acked-by: Daniel Stone <daniels@collabora.com> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5804>
2020-07-07 21:02:35 +08:00
- *ignore_scheduled_pipelines
ci: Add "is forked branch" YAML anchor Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6566>
2020-09-08 23:52:24 +08:00
- if: *is-forked-branch
gitlab-ci: Use all_paths in .test-manual rules Without this, the .test-manual jobs could end up as 'when: manual' when the jobs they depend on were 'when: never', which was flagged as invalid YAML, preventing the pipeline from being created. Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4522>
2020-04-11 21:32:02 +08:00
changes:
*all_paths
when: manual
- when: never
ci: Manual test jobs don't need the Git tree If they do need something, it should be passed via artifacts from a build job. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7904>
2020-12-04 01:59:25 +08:00
variables:
GIT_STRATEGY: none
ci: Let manual LAVA jobs have a longer timeout than others So far only LAVA jobs make use of it, but I guess baremetal could be extended to have these timeouts as well. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13441>
2021-10-22 22:23:21 +08:00
JOB_TIMEOUT: 80
ci: Move db820c and db410c's gles3 tests to manual, like radv did. This should make these tests available for clicking on the web ui in personal branches, while hiding them from marge and the post-merge CI pipelines. We had already disabled db410c's gles3, but it wasn't available in the ui and you had to hack .gitalb-ci.yml. db820c is now being disabled by default, due to instaboots mentioned in https://gitlab.freedesktop.org/mesa/mesa/issues/2649 Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4247>
2020-03-20 02:45:01 +08:00
gitlab-ci: rule anchor for experimental devices as manual in MRs We want to give developers the option to run their jobs on devices that are still being stabilized in the CI infrastructure. These jobs should be optional and not prevent merging from happening. The is-forked-branch-or-pre-merge anchor was not being used anywhere, so it was changed to is-forked-branch-or-pre-merge-not-for-marge to create this new rule. Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10405>
2021-04-22 19:17:40 +08:00
# The above .test-manual rules doesn't allow the jobs to be available for MRs
# but we should have an option to have manual jobs in MRs as well.
.test-manual-mr:
rules:
- *ignore_scheduled_pipelines
- if: *is-forked-branch-or-pre-merge-not-for-marge
changes:
*all_paths
when: manual
- when: never
variables:
GIT_STRATEGY: none
ci: Let manual LAVA jobs have a longer timeout than others So far only LAVA jobs make use of it, but I guess baremetal could be extended to have these timeouts as well. Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13441>
2021-10-22 22:23:21 +08:00
JOB_TIMEOUT: 80
gitlab-ci: rule anchor for experimental devices as manual in MRs We want to give developers the option to run their jobs on devices that are still being stabilized in the CI infrastructure. These jobs should be optional and not prevent merging from happening. The is-forked-branch-or-pre-merge anchor was not being used anywhere, so it was changed to is-forked-branch-or-pre-merge-not-for-marge to create this new rule. Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10405>
2021-04-22 19:17:40 +08:00
ci: Make a simple little bare-metal fastboot mode for db410c. This supports powering up the device (using an external tool you provide based on your particular lab), talking over serial to wait for the fastboot prompt, and then booting a fastboot image on a target device. I was previously relying on LAVA for this, but that ran afoul of corporate policies related to the AGPL. However, LAVA wasn't doing too much for us, given that gitlab already has a job scheduler and tagging and runners. We were spending a lot of engineering on making the two systems match up, when we can just have gitlab do it directly. Lightly-reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076>
2020-03-04 06:38:09 +08:00
.baremetal-test:
extends:
- .ci-run-policy
ci/bare-metal: Use the deqp-runner bits straight out of the artifacts. We've already uploaded and downloaded them from fd.o and put them in the rootfs, so we can clean up the extra prep work. Our test job now extends from .test so that the artifacts' install dir with all the scripts is extracted. This required moving the dependency on meson-testing to the x86 test-gl/test-vk job blocks. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5393>
2020-06-09 06:09:51 +08:00
- .test
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
ci: Make a simple little bare-metal fastboot mode for db410c. This supports powering up the device (using an external tool you provide based on your particular lab), talking over serial to wait for the fastboot prompt, and then booting a fastboot image on a target device. I was previously relying on LAVA for this, but that ran afoul of corporate policies related to the AGPL. However, LAVA wasn't doing too much for us, given that gitlab already has a job scheduler and tagging and runners. We were spending a lot of engineering on making the two systems match up, when we can just have gitlab do it directly. Lightly-reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076>
2020-03-04 06:38:09 +08:00
stage: test
ci/freedreno: Use the http cache for artifacts downloads, too. The gitlab artifacts handling has been slow in the past as we hit gitlab.fdo from multiple runners, and it costs fd.o egress bandwidth. Use the local http cache against the packet.net minio to cut that downloads cost. Closes: #3249 Reviewed-by: Daniel Stone <daniel@fooishbar.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8727>
2021-01-22 07:41:18 +08:00
before_script:
ci: Uprev piglit Bring up the piglit replay jwt-file argument feature. Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14004>
2021-12-02 21:10:26 +08:00
- !reference [default, before_script]
ci/freedreno: Use the http cache for artifacts downloads, too. The gitlab artifacts handling has been slow in the past as we hit gitlab.fdo from multiple runners, and it costs fd.o egress bandwidth. Use the local http cache against the packet.net minio to cut that downloads cost. Closes: #3249 Reviewed-by: Daniel Stone <daniel@fooishbar.org> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8727>
2021-01-22 07:41:18 +08:00
# Use this instead of gitlab's artifacts download because it hits packet.net
# instead of fd.o. Set FDO_HTTP_CACHE_URI to an http cache for your test lab to
# improve it even more (see https://docs.mesa3d.org/ci/bare-metal.html for
# setup).
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
- wget ${FDO_HTTP_CACHE_URI:-}https://${PIPELINE_ARTIFACTS_BASE}/${MINIO_ARTIFACT_NAME}.tar.gz -S --progress=dot:giga -O- | tar -xz
ci: Switch cheza (freedreno a630) testing to baremetal. Now that we have scripts in place to do baremetal testing of cheza, switch it over. As of this writing, we have 5 chezas for baremetal and 4 for the old docker CI setup (just 2 fewer than we originally had before this work, since some had had filesystem failures and I switched those first), and once we are sure of this we can backport to stable branch CI and move the rest of them to baremetal. I've run a lot of jobs through the baremetal scripts as I worked on sorting out vulkan CTS stability, so I feel good about the stability of the GLES CTS here. The options job is now split out to separate jobs, as we don't currently have a way to stack multiple sets deqp runs with different env vars in a single baremetal run, and just chaining cros_servo.sh invocations runs into a lack of cleanup of the serial-watching scripts which we rely on container exit sorting out for us. This means a little less than 2x the artifacts downloads we had before for a630 and a few more container instantiations. Reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5247>
2020-05-16 02:22:37 +08:00
artifacts:
when: always
name: "mesa_${CI_JOB_NAME}"
paths:
- results/
- serial*.txt
ci/deqp: Move .shader_cache artifacts exclusion to the yml. Less noise in the job log when we want to be highlighting deqp-runner's output. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8206>
2020-12-22 02:55:40 +08:00
exclude:
- results/*.shader_cache
ci/deqp: Upgrade the runner, enable junit output. I moved QPA-to-XML conversion to the runner, so Mesa CI (and developers!) don't need to do quite so much in bash. I also made it clean up caselist .qpa files since nobody ever wants them and we deleted them anyway. This cleans up a ton of the job log output. Additionally, I added a subcommend to turn the .csv into a junit output that we can expose to gitlab. Now, the pipeline's status page will report the failed testcases, and the "detail" button will give you a link to the .XML to view for the failure. (We don't report all testcases because it's too much load for the gitlab server). Note that this will 404 for the LAVA runners for now, as they don't retain artifacts in gitlab (the plan is to eventually have them minio upload the artifacts). This uprev also includes a deqp output parsing fix, resulting in us catching a couple more failures in some drivers. Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8206>
2020-12-19 08:47:51 +08:00
reports:
junit: results/junit.xml
ci: Make a simple little bare-metal fastboot mode for db410c. This supports powering up the device (using an external tool you provide based on your particular lab), talking over serial to wait for the fastboot prompt, and then booting a fastboot image on a target device. I was previously relying on LAVA for this, but that ran afoul of corporate policies related to the AGPL. However, LAVA wasn't doing too much for us, given that gitlab already has a job scheduler and tagging and runners. We were spending a lot of engineering on making the two systems match up, when we can just have gitlab do it directly. Lightly-reviewed-by: Kristian H. Kristensen <hoegsberg@google.com> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4076>
2020-03-04 06:38:09 +08:00
ci/v3d: Add V3D and V3DV testing Add OpenGL and Vulkan testing for V3D and V3DV respectively. Add also a couple of manual piglit jobs for V3D. v2: - Replace custom mustpass with running fraction of tests (Eric) 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>
2021-02-12 20:29:19 +08:00
.baremetal-test-armhf:
extends:
- .baremetal-test
variables:
ci/bare-metal: armhf: move BM_ROOTFS to generic place Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13751>
2021-11-10 22:48:50 +08:00
BM_ROOTFS: /rootfs-armhf
ci: Allow better customization of the name of the artifacts for minio. To have asan testing, we need two different sets of artifacts per arch. Plus, "UPLOAD_FOR_LAVA" was misnamed at this point anyway. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2021-02-16 04:35:41 +08:00
MINIO_ARTIFACT_NAME: mesa-armhf
ci/v3d: Add V3D and V3DV testing Add OpenGL and Vulkan testing for V3D and V3DV respectively. Add also a couple of manual piglit jobs for V3D. v2: - Replace custom mustpass with running fraction of tests (Eric) 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>
2021-02-12 20:29:19 +08:00
ci/bare-metal: add .baremetal-test-arm64 Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com> Reviewed-by: Emma Anholt <emma@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13751>
2021-11-10 22:54:57 +08:00
.baremetal-test-arm64:
extends:
- .baremetal-test
variables:
BM_ROOTFS: /rootfs-arm64
MINIO_ARTIFACT_NAME: mesa-arm64
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
.baremetal-arm64-asan-test:
variables:
ci/deqp-runner: Move remaining asan runs to --env LD_PRELOAD= This should improve their reliability and speed a little by getting deqp-runner off of asan. This removes the last jobs setting TEST_LD_PRELOAD, so remove passing that variable around from other scripts. Acked-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13372>
2021-10-12 07:07:23 +08:00
DEQP_RUNNER_OPTIONS: "--env LD_PRELOAD=libasan.so.6"
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
MINIO_ARTIFACT_NAME: mesa-arm64-asan
needs:
ci: Add debian/ prefix to job names for Debian based docker images And move the image build scripts to a subdirectory correspondingly. Preparation for adding images based on other OSs. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-15 23:42:22 +08:00
- debian/arm_test
ci: Rename Debian based build jobs from meson-* to debian-* meson has been the only build system in tree for some time, so the meson- prefix was a bit meaningless. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11412>
2021-06-16 00:23:33 +08:00
- job: debian-arm64-asan
ci/freedreno: Add a fractional gles31 run with asan enabled. We have to disable the GLSL unit tests because with asan it runs way too much code under qemu and times out. Those unit tests have coverage on x86, anyway. I also included a vulkan run, which is disabled by default due to timeouts that I need to sort out still. It should be a useful tool for turnip devs, though. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9070>
2020-12-16 07:47:51 +08:00
artifacts: false
ci: refactor arm64 jobs in preparation for piglit addition v2: - Rename the ".arm64-deqp-test-vk" template as ".arm64-deqp-test-freedreno-vk" (Eric). v3: - Rename the ".arm64-test" template as ".freedreno-test" (Eric). - Rename the ".arm64-deqp-test" template as ".baremetal-deqp-test" (Eric). - Rename the ".arm64-deqp-test-freedreno-vk" template as ".baremetal-deqp-test-freedreno-vk". Signed-off-by: Andres Gomez <agomez@igalia.com> Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6388>
2020-11-15 03:50:18 +08:00
.baremetal-deqp-test:
variables:
ci: Unify {BARE_METAL,LAVA}_TEST_SCRIPT environment Should also probably never have been different. Signed-off-by: Daniel Stone <daniels@collabora.com> Acked-by: Martin Peres <martin.peres@mupuf.org> Acked-by: Emma Anholt <emma@anholt.net> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11337>
2021-06-11 23:53:54 +08:00
HWCI_TEST_SCRIPT: "/install/deqp-runner.sh"
ci/deqp-runner: Simplify the --jobs argument setup. We can use the general "how parallel should we go on this runner?" env var and save a bunch of massaging env var names. Fixes how PIGLIT_PARALLEL looked like it was useful but actually wasn't passed through to HW runners. Reviewed-by: Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/13372>
2021-10-12 07:03:47 +08:00
FDO_CI_CONCURRENT: 0 # Default to number of CPUs
Reference in New Issue Copy Permalink