From: Vignesh Raman <vignesh.raman@collabora.com>
To: jim.cromie@gmail.com
Cc: linux-kernel@vger.kernel.org, helen.fornazier@gmail.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm/ci: bump IGT version to v2.3
Date: Mon, 4 May 2026 10:13:17 +0530 [thread overview]
Message-ID: <cfc9c37f-fac3-4e71-a4b5-22de26de0ee1@collabora.com> (raw)
In-Reply-To: <db70ec3b-736f-478c-917c-f8a56726c13e@collabora.com>
HI Jim,
On 06/04/26 12:16, Vignesh Raman wrote:
> Hi Jim,
>
> On 04/04/26 18:38, jim.cromie@gmail.com wrote:
>> On Tue, Mar 31, 2026 at 11:45 PM Vignesh Raman
>> <vignesh.raman@collabora.com> wrote:
>>>
>>> Hi Jim,
>>>
>>> On 19/03/26 21:41, Jim Cromie wrote:
>>>> IGT_VERSION is currently pinned to a sha thats ~1100 behind HEAD
>>>>
>>>> Lets bump it to the latest milestone/tag at v2.3
>>>> Thats now only ~630 behind.
>>>> Can we haz a v2.4 ?
>>>>
>>>> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
>>>> ---
>>>> drivers/gpu/drm/ci/gitlab-ci.yml | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/ci/gitlab-ci.yml b/drivers/gpu/drm/ci/
>>>> gitlab-ci.yml
>>>> index 56638814bb28..d546bd123a63 100644
>>>> --- a/drivers/gpu/drm/ci/gitlab-ci.yml
>>>> +++ b/drivers/gpu/drm/ci/gitlab-ci.yml
>>>> @@ -5,7 +5,7 @@ variables:
>>>> UPSTREAM_REPO: https://gitlab.freedesktop.org/drm/kernel.git
>>>> TARGET_BRANCH: drm-next
>>>>
>>>> - IGT_VERSION: 129d5b10baaadea1d6cd6377341c4cb42e7ee6fd
>>>> + IGT_VERSION: v2.3
>>>
>>> Thanks for the patch. We also need to update the expectation files along
>>> with this igt uprev. Are you planning to do it?
>>>
>>
>> I dont know what that means / entails,
>> So, it's best I don't.
>> When you do it, I'll then know how (if you cc me ;-)
>
> When mesa or IGT version is updated in drm-ci, we need to update the
> fails/flakes files in the xfails folder, as the new uprev can introduce
> new failures or make some tests pass.
>
> Example https://gitlab.freedesktop.org/drm/msm/-/merge_requests/213/
> diffs?commit_id=af95dfd73f307ce1bf4ba40826aabca3b60ceb84
>
> I will pick up your patch and run some tests, and update you. Thanks.
I updated igt to v2.4 and ran the pipeline and updated fails.
https://gitlab.freedesktop.org/vigneshraman/msm/-/commit/13cf56b5e0b7ce2d252ecd5849c1cba3881b1c22
https://gitlab.freedesktop.org/vigneshraman/msm/-/pipelines/1658019
Need to investigate the failures and see if it is caused due to
test issue or it is actual failure in driver.
Regards,
Vignesh
>
> Regards,
> Vignesh
>
>>
>>
>>
>>> Regards,
>>> Vignesh
>>>
>>>>
>>>> DEQP_RUNNER_GIT_URL: https://gitlab.freedesktop.org/mesa/deqp-
>>>> runner.git
>>>> DEQP_RUNNER_GIT_TAG: v0.20.0
>>>
>
next prev parent reply other threads:[~2026-05-04 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:11 [PATCH 1/1] drm/ci: bump IGT version to v2.3 Jim Cromie
2026-03-31 15:55 ` Dixit, Ashutosh
2026-04-01 5:44 ` Vignesh Raman
2026-04-04 13:08 ` jim.cromie
2026-04-06 6:46 ` Vignesh Raman
2026-05-04 4:43 ` Vignesh Raman [this message]
2026-05-04 14:36 ` jim.cromie
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=cfc9c37f-fac3-4e71-a4b5-22de26de0ee1@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helen.fornazier@gmail.com \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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