From: Vignesh Raman <vignesh.raman@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, lumag@kernel.org, robdclark@gmail.com,
robin.clark@oss.qualcomm.com, guilherme.gallo@collabora.com,
sergi.blanch.torne@collabora.com, valentine.burley@collabora.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.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 6/7] drm/ci: uprev IGT
Date: Tue, 10 Feb 2026 12:49:46 +0530 [thread overview]
Message-ID: <5ed6508c-78ab-4606-b503-9bc54f5cdea9@collabora.com> (raw)
In-Reply-To: <5vxrhiilcsaull2airasmc3pjqazvswrtojozz264i5vk3m6zl@pgkdwq46p4ho>
Hi Dmitry,
On 27/01/26 19:55, Dmitry Baryshkov wrote:
> On Tue, Jan 27, 2026 at 06:26:11PM +0530, Vignesh Raman wrote:
>> Hi Dmitry,
>>
>> On 27/01/26 18:01, Dmitry Baryshkov wrote:
>>> On Tue, Jan 27, 2026 at 04:14:01PM +0530, Vignesh Raman wrote:
>>>> Recent IGT [1] seems to be broken on MSM hardware, with many tests
>>>> failing due to the old_primary->index != 0 assertion. Uprev IGT to
>>>> the last known good revision where the tests pass, and update the
>>>> expectation files accordingly.
>>>>
>>>> [1] https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/a909ab05
>>>>
>>>> Signed-off-by: Vignesh Raman <vignesh.raman@collabora.com>
>>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>>>
>>> It is not clear, which parts here are due to Mesa uprev (yes, there are
>>> some of those) and which are due to the IGT uprev. Please split into two
>>> commits and make sure that Mesa-uprev passes more or less clearly.
>>
>> The mesa uprev and the IGT uprev are already split into two separate
>> commits. The IGT uprev only updates the IGT version in gitlab-ci.yml and
>> xfails.
>
> I think I was not clear enough: Mesa uprev also causes some of the
> xfails. Those needs to be a part of the Mesa uprev commit.
I have created v2 where the mesa uprev commit also includes the updated
xfails. I will send IGT uprev as a separate commit/series.
https://lore.kernel.org/dri-devel/20260210071138.2256773-1-vignesh.raman@collabora.com/T/#t
Regards,
Vignesh
>
>
next prev parent reply other threads:[~2026-02-10 7:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 10:43 [PATCH v1 0/7] drm/ci: add new jobs, uprev IGT and mesa Vignesh Raman
2026-01-27 10:43 ` [PATCH v1 1/7] drm/ci: uprev mesa Vignesh Raman
2026-01-27 10:43 ` [PATCH v1 2/7] drm/ci: move qualcomm baremetal jobs to lava Vignesh Raman
2026-01-27 10:43 ` [PATCH v1 3/7] drm/ci: reduce sm8350-hdk parallel jobs from 4 to 2 Vignesh Raman
2026-01-27 11:20 ` Dmitry Baryshkov
2026-01-27 10:43 ` [PATCH v1 4/7] drm/ci: i915: cml: update runner tag Vignesh Raman
2026-01-27 10:44 ` [PATCH v1 5/7] drm/ci: add rk3588-rock-5b Vignesh Raman
2026-01-27 10:44 ` [PATCH v1 6/7] drm/ci: uprev IGT Vignesh Raman
2026-01-27 12:31 ` Dmitry Baryshkov
2026-01-27 12:56 ` Vignesh Raman
2026-01-27 14:25 ` Dmitry Baryshkov
2026-02-10 7:19 ` Vignesh Raman [this message]
2026-01-27 10:44 ` [PATCH v1 7/7] drm/ci: disable rebase when pulling *-external-fixes Vignesh Raman
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=5ed6508c-78ab-4606-b503-9bc54f5cdea9@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.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=lumag@kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.clark@oss.qualcomm.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=valentine.burley@collabora.com \
--cc=virtualization@lists.linux.dev \
/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