From: Vignesh Raman <vignesh.raman@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: daniels@collabora.com, helen.koike@collabora.com,
airlied@gmail.com, daniel@ffwll.ch, robdclark@gmail.com,
david.heidelberg@collabora.com, guilherme.gallo@collabora.com,
sergi.blanch.torne@collabora.com, dmitry.baryshkov@linaro.org,
mcanal@igalia.com, linux-mediatek@lists.infradead.org,
linux-amlogic@lists.infradead.org,
linux-rockchip@lists.infradead.org,
amd-gfx@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
intel-gfx@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/4] Uprev mesa and IGT
Date: Tue, 23 Apr 2024 09:32:39 +0530 [thread overview]
Message-ID: <20240423040243.448091-1-vignesh.raman@collabora.com> (raw)
Uprev mesa and IGT to the latest version. Stop vendoring the
testlist into the kernel. Instead, use the testlist from the
IGT build to ensure we do not miss renamed or newly added tests.
Update the xfails with the latest testlist run.
Also build virtual GPU driver for virtio as module.
This series also includes patch to add vkms testing to drm-ci.
The flakes list needs to be updated upsteam. Will send it
after this series is reviewed.
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1161026
Vignesh Raman (4):
drm/ci: uprev mesa version
drm/ci: build virtual GPU driver as module
drm/ci: uprev IGT and generate testlist from build
drm/ci: add tests on vkms
MAINTAINERS | 1 +
drivers/gpu/drm/ci/build-igt.sh | 23 +
drivers/gpu/drm/ci/build.sh | 2 +-
drivers/gpu/drm/ci/container.yml | 12 +-
drivers/gpu/drm/ci/gitlab-ci.yml | 14 +-
drivers/gpu/drm/ci/igt_runner.sh | 15 +-
drivers/gpu/drm/ci/image-tags.yml | 7 +-
drivers/gpu/drm/ci/test.yml | 33 +-
drivers/gpu/drm/ci/testlist.txt | 2761 -----------------
drivers/gpu/drm/ci/x86_64.config | 3 +-
.../gpu/drm/ci/xfails/amdgpu-stoney-fails.txt | 45 +-
.../drm/ci/xfails/amdgpu-stoney-flakes.txt | 15 +-
.../gpu/drm/ci/xfails/amdgpu-stoney-skips.txt | 30 +-
drivers/gpu/drm/ci/xfails/i915-amly-fails.txt | 27 +
.../gpu/drm/ci/xfails/i915-amly-flakes.txt | 9 +
drivers/gpu/drm/ci/xfails/i915-amly-skips.txt | 22 +-
drivers/gpu/drm/ci/xfails/i915-apl-fails.txt | 47 +-
drivers/gpu/drm/ci/xfails/i915-apl-skips.txt | 24 +-
drivers/gpu/drm/ci/xfails/i915-cml-fails.txt | 37 +-
drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt | 6 +
drivers/gpu/drm/ci/xfails/i915-cml-skips.txt | 20 +
drivers/gpu/drm/ci/xfails/i915-glk-fails.txt | 37 +-
drivers/gpu/drm/ci/xfails/i915-glk-skips.txt | 21 +-
drivers/gpu/drm/ci/xfails/i915-kbl-fails.txt | 29 +-
drivers/gpu/drm/ci/xfails/i915-kbl-flakes.txt | 1 -
drivers/gpu/drm/ci/xfails/i915-kbl-skips.txt | 34 +-
drivers/gpu/drm/ci/xfails/i915-tgl-fails.txt | 27 +-
drivers/gpu/drm/ci/xfails/i915-tgl-flakes.txt | 6 +
drivers/gpu/drm/ci/xfails/i915-tgl-skips.txt | 28 +-
drivers/gpu/drm/ci/xfails/i915-whl-fails.txt | 57 +-
drivers/gpu/drm/ci/xfails/i915-whl-skips.txt | 21 +-
.../drm/ci/xfails/mediatek-mt8173-fails.txt | 47 +-
.../drm/ci/xfails/mediatek-mt8173-skips.txt | 13 +
.../drm/ci/xfails/mediatek-mt8183-fails.txt | 18 +-
.../drm/ci/xfails/mediatek-mt8183-flakes.txt | 6 +
.../drm/ci/xfails/mediatek-mt8183-skips.txt | 15 +
.../gpu/drm/ci/xfails/meson-g12b-fails.txt | 20 +-
.../gpu/drm/ci/xfails/meson-g12b-flakes.txt | 7 +
.../gpu/drm/ci/xfails/meson-g12b-skips.txt | 15 +
.../gpu/drm/ci/xfails/msm-apq8016-fails.txt | 25 +-
.../gpu/drm/ci/xfails/msm-apq8016-flakes.txt | 7 +
.../gpu/drm/ci/xfails/msm-apq8016-skips.txt | 15 +
.../gpu/drm/ci/xfails/msm-apq8096-fails.txt | 6 +-
.../gpu/drm/ci/xfails/msm-apq8096-flakes.txt | 6 +
.../gpu/drm/ci/xfails/msm-apq8096-skips.txt | 117 +-
.../msm-sc7180-trogdor-kingoftown-fails.txt | 40 +-
.../msm-sc7180-trogdor-kingoftown-flakes.txt | 6 +
.../msm-sc7180-trogdor-kingoftown-skips.txt | 16 +
...sm-sc7180-trogdor-lazor-limozeen-fails.txt | 41 +-
...m-sc7180-trogdor-lazor-limozeen-flakes.txt | 11 +
...sm-sc7180-trogdor-lazor-limozeen-skips.txt | 16 +
.../gpu/drm/ci/xfails/msm-sdm845-fails.txt | 76 +-
.../gpu/drm/ci/xfails/msm-sdm845-flakes.txt | 26 +-
.../gpu/drm/ci/xfails/msm-sdm845-skips.txt | 16 +
.../drm/ci/xfails/rockchip-rk3288-fails.txt | 54 -
.../drm/ci/xfails/rockchip-rk3288-skips.txt | 60 +-
.../drm/ci/xfails/rockchip-rk3399-fails.txt | 79 +-
.../drm/ci/xfails/rockchip-rk3399-flakes.txt | 13 +-
.../drm/ci/xfails/rockchip-rk3399-skips.txt | 17 +-
.../drm/ci/xfails/virtio_gpu-none-fails.txt | 99 +-
.../drm/ci/xfails/virtio_gpu-none-skips.txt | 19 +-
drivers/gpu/drm/ci/xfails/vkms-none-fails.txt | 46 +
.../gpu/drm/ci/xfails/vkms-none-flakes.txt | 21 +
drivers/gpu/drm/ci/xfails/vkms-none-skips.txt | 30 +
64 files changed, 1109 insertions(+), 3308 deletions(-)
delete mode 100644 drivers/gpu/drm/ci/testlist.txt
create mode 100644 drivers/gpu/drm/ci/xfails/i915-amly-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt
delete mode 100644 drivers/gpu/drm/ci/xfails/i915-kbl-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/i915-tgl-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/mediatek-mt8173-skips.txt
create mode 100644 drivers/gpu/drm/ci/xfails/mediatek-mt8183-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/mediatek-mt8183-skips.txt
create mode 100644 drivers/gpu/drm/ci/xfails/meson-g12b-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/meson-g12b-skips.txt
create mode 100644 drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/msm-apq8016-skips.txt
create mode 100644 drivers/gpu/drm/ci/xfails/msm-apq8096-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/msm-sc7180-trogdor-kingoftown-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/msm-sc7180-trogdor-lazor-limozeen-flakes.txt
delete mode 100644 drivers/gpu/drm/ci/xfails/rockchip-rk3288-fails.txt
create mode 100644 drivers/gpu/drm/ci/xfails/vkms-none-fails.txt
create mode 100644 drivers/gpu/drm/ci/xfails/vkms-none-flakes.txt
create mode 100644 drivers/gpu/drm/ci/xfails/vkms-none-skips.txt
--
2.40.1
next reply other threads:[~2024-04-23 4:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 4:02 Vignesh Raman [this message]
2024-04-23 4:02 ` [PATCH v1 1/4] drm/ci: uprev mesa version Vignesh Raman
2024-04-23 4:02 ` [PATCH v1 2/4] drm/ci: build virtual GPU driver as module Vignesh Raman
2024-04-23 4:02 ` [PATCH v1 3/4] drm/ci: uprev IGT and generate testlist from build Vignesh Raman
2024-04-23 10:24 ` Maíra Canal
2024-04-23 12:23 ` Dmitry Baryshkov
2024-04-23 12:56 ` Vignesh Raman
2024-04-23 4:02 ` [PATCH v1 4/4] drm/ci: add tests on vkms Vignesh Raman
2024-04-23 4:41 ` ✗ Fi.CI.CHECKPATCH: warning for Uprev mesa and IGT Patchwork
2024-04-23 4:49 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-24 6:35 ` ✗ Fi.CI.IGT: failure " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240423040243.448091-1-vignesh.raman@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=david.heidelberg@collabora.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.koike@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mcanal@igalia.com \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).