mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Helen Mae Koike Fornazier <helen.koike@collabora.com>
To: "Vignesh Raman" <vignesh.raman@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>,
	"deborah.brouwer" <deborah.brouwer@collabora.com>,
	"dmitry.baryshkov" <dmitry.baryshkov@linaro.org>,
	"mripard" <mripard@kernel.org>,
	"rodrigo.vivi" <rodrigo.vivi@intel.com>,
	"quic_abhinavk" <quic_abhinavk@quicinc.com>,
	"linux-mediatek" <linux-mediatek@lists.infradead.org>,
	"linux-amlogic" <linux-amlogic@lists.infradead.org>,
	"linux-rockchip" <linux-rockchip@lists.infradead.org>,
	"amd-gfx" <amd-gfx@lists.freedesktop.org>,
	"linux-arm-msm" <linux-arm-msm@vger.kernel.org>,
	"intel-gfx" <intel-gfx@lists.freedesktop.org>,
	"virtualization" <virtualization@lists.linux.dev>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] docs/gpu: ci: update flake tests requirements
Date: Thu, 03 Oct 2024 11:09:24 -0300	[thread overview]
Message-ID: <19252b6cc3e.e564b8892647525.6443730088827538481@collabora.com> (raw)
In-Reply-To: <20240930095255.2071586-1-vignesh.raman@collabora.com>





---- On Mon, 30 Sep 2024 06:52:47 -0300 Vignesh Raman  wrote ---

 > Update the documentation to specify linking to a relevant GitLab 
 > issue or email report for each new flake entry. Added specific 
 > GitLab issue urls for amdgpu, i915, msm and xe driver. 
 >  
 > Acked-by: Maxime Ripard mripard@kernel.org> 
 > Acked-by: Rodrigo Vivi rodrigo.vivi@intel.com> #intel and xe 
 > Acked-by: Abhinav Kumar quic_abhinavk@quicinc.com> # msm 
 > Acked-by: Dmitry Baryshkov dmitry.baryshkov@linaro.org> # msm 
 > Signed-off-by: Vignesh Raman vignesh.raman@collabora.com> 

Applied to drm-misc-next
Thanks!

Helen

 > --- 
 >  
 > v2: 
 > - Add gitlab issue link for msm driver. 
 >  
 > v3: 
 > - Update docs to specify we use email reporting or GitLab issues for flake entries. 
 >  
 > v4: 
 > - Add gitlab issue link for xe driver. 
 >  
 > --- 
 >  Documentation/gpu/automated_testing.rst | 14 ++++++++++---- 
 >  1 file changed, 10 insertions(+), 4 deletions(-) 
 >  
 > diff --git a/Documentation/gpu/automated_testing.rst b/Documentation/gpu/automated_testing.rst 
 > index 2d5a28866afe..6d7c6086034d 100644 
 > --- a/Documentation/gpu/automated_testing.rst 
 > +++ b/Documentation/gpu/automated_testing.rst 
 > @@ -68,19 +68,25 @@ known to behave unreliably. These tests won't cause a job to fail regardless of 
 >  the result. They will still be run. 
 >  
 >  Each new flake entry must be associated with a link to the email reporting the 
 > -bug to the author of the affected driver, the board name or Device Tree name of 
 > -the board, the first kernel version affected, the IGT version used for tests, 
 > -and an approximation of the failure rate. 
 > +bug to the author of the affected driver or the relevant GitLab issue. The entry 
 > +must also include the board name or Device Tree name, the first kernel version 
 > +affected, the IGT version used for tests, and an approximation of the failure rate. 
 >  
 >  They should be provided under the following format:: 
 >  
 > -  # Bug Report: $LORE_OR_PATCHWORK_URL 
 > +  # Bug Report: $LORE_URL_OR_GITLAB_ISSUE 
 >  # Board Name: broken-board.dtb 
 >  # Linux Version: 6.6-rc1 
 >  # IGT Version: 1.28-gd2af13d9f 
 >  # Failure Rate: 100 
 >  flaky-test 
 >  
 > +Use the appropriate link below to create a GitLab issue: 
 > +amdgpu driver: https://gitlab.freedesktop.org/drm/amd/-/issues 
 > +i915 driver: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues 
 > +msm driver: https://gitlab.freedesktop.org/drm/msm/-/issues 
 > +xe driver: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues 
 > + 
 >  drivers/gpu/drm/ci/${DRIVER_NAME}-${HW_REVISION}-skips.txt 
 >  ----------------------------------------------------------- 
 >  
 > -- 
 > 2.43.0 
 >  
 > 

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2024-10-03 14:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  9:52 Vignesh Raman
2024-10-01 13:50 ` Vignesh Raman
2024-10-02 18:50   ` Deucher, Alexander
2024-10-03 14:09 ` Helen Mae Koike Fornazier [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=19252b6cc3e.e564b8892647525.6443730088827538481@collabora.com \
    --to=helen.koike@collabora.com \
    --cc=airlied@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=deborah.brouwer@collabora.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@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=mripard@kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=vignesh.raman@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

all inboxes | Powered by JetHome®