mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raman <vignesh.raman@collabora.com>
To: Helen Mae Koike Fornazier <helen.koike@collabora.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	daniels <daniels@collabora.com>, airlied <airlied@gmail.com>,
	daniel <daniel@ffwll.ch>, robdclark <robdclark@gmail.com>,
	"guilherme.gallo" <guilherme.gallo@collabora.com>,
	"sergi.blanch.torne" <sergi.blanch.torne@collabora.com>,
	"jani.nikula" <jani.nikula@linux.intel.com>,
	"dmitry.baryshkov" <dmitry.baryshkov@linaro.org>,
	mripard <mripard@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] drm/ci: uprev mesa and modify gitlab rules
Date: Wed, 4 Dec 2024 07:53:08 +0530	[thread overview]
Message-ID: <a9a956b7-55da-4b90-bf82-92def097a63a@collabora.com> (raw)
In-Reply-To: <1938cdd3a4b.10ab98f77527721.7719837795987945098@collabora.com>

Hi Helen,

On 03/12/24 19:42, Helen Mae Koike Fornazier wrote:
> Hi Vignesh,
> 
> Thanks for your patchset.
> 
> 
> 
> ---- On Thu, 28 Nov 2024 01:20:19 -0300 Vignesh Raman  wrote ---
> 
>   > Uprev mesa to adapt to the latest changes in mesa-ci,
>   > including new container jobs and stages. Update the
>   > lava-submit script to align with recent mesa-ci changes
>   > for using LAVA rootfs overlays. Modify gitLab rules
>   > to include scheduled pipelines.
>   >
>   > Pipeline link,
>   > https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1318024
> 
> I see this pipeline has a few failures, most of them are because outdated xfails files and timeouts.
> Could we fix that first? So when we test this patchset we can verify if it introduces any issues or not.

Yes. The expectation files are not updated. I will uprev IGT and rerun 
the tests and update xfails.

Regards,
Vignesh

> 
> Thanks
> Helen
> 
>   >
>   > Vignesh Raman (2):
>   >  drm/ci: uprev mesa
>   >  drm/ci: update gitlab rules
>   >
>   >  drivers/gpu/drm/ci/build.sh       |   2 +-
>   >  drivers/gpu/drm/ci/build.yml      | 104 ++++++++++++++++-
>   >  drivers/gpu/drm/ci/container.yml  |  22 ++--
>   >  drivers/gpu/drm/ci/gitlab-ci.yml  | 185 ++++++++++++++++--------------
>   >  drivers/gpu/drm/ci/image-tags.yml |  11 +-
>   >  drivers/gpu/drm/ci/lava-submit.sh |  99 +++++++++++-----
>   >  drivers/gpu/drm/ci/test.yml       |  33 +++---
>   >  7 files changed, 314 insertions(+), 142 deletions(-)
>   >
>   > --
>   > 2.43.0
>   >
>   >
> 

      reply	other threads:[~2024-12-04  2:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  4:20 Vignesh Raman
2024-11-28  4:20 ` [PATCH v1 1/2] drm/ci: uprev mesa Vignesh Raman
2024-12-03 14:14   ` Helen Mae Koike Fornazier
2024-11-28  4:20 ` [PATCH v1 2/2] drm/ci: update gitlab rules Vignesh Raman
2024-12-03 14:12 ` [PATCH v1 0/2] drm/ci: uprev mesa and modify " Helen Mae Koike Fornazier
2024-12-04  2:23   ` Vignesh Raman [this message]

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=a9a956b7-55da-4b90-bf82-92def097a63a@collabora.com \
    --to=vignesh.raman@collabora.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=robdclark@gmail.com \
    --cc=sergi.blanch.torne@collabora.com \
    /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

all inboxes | Powered by JetHome®