From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Vignesh Raman <vignesh.raman@collabora.com>
Cc: <dri-devel@lists.freedesktop.org>, <daniels@collabora.com>,
<helen.koike@collabora.com>, <airlied@gmail.com>,
<daniel@ffwll.ch>, <robdclark@gmail.com>,
<guilherme.gallo@collabora.com>,
<sergi.blanch.torne@collabora.com>,
<deborah.brouwer@collabora.com>, <dmitry.baryshkov@linaro.org>,
<mripard@kernel.org>, <quic_abhinavk@quicinc.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 v3] docs/gpu: ci: update flake tests requirements
Date: Fri, 27 Sep 2024 10:35:58 -0400 [thread overview]
Message-ID: <ZvbCzqvyeTI_j2cD@intel.com> (raw)
In-Reply-To: <20240927052416.1833889-1-vignesh.raman@collabora.com>
On Fri, Sep 27, 2024 at 10:54:14AM +0530, 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 i915, msm and amdgpu driver.
>
> 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>
> ---
>
> v2:
> - Add gitlab issue link for msm driver.
>
> v3:
> - Update docs to specify we use email reporting or GitLab issues for flake entries.
>
> ---
> Documentation/gpu/automated_testing.rst | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/gpu/automated_testing.rst b/Documentation/gpu/automated_testing.rst
> index 2d5a28866afe..03769b4a17cf 100644
> --- a/Documentation/gpu/automated_testing.rst
> +++ b/Documentation/gpu/automated_testing.rst
> @@ -68,19 +68,24 @@ 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
Probably good to add:
xe driver: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues
Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> +msm driver: https://gitlab.freedesktop.org/drm/msm/-/issues
> +
> drivers/gpu/drm/ci/${DRIVER_NAME}-${HW_REVISION}-skips.txt
> -----------------------------------------------------------
>
> --
> 2.43.0
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-09-27 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 5:24 [PATCH v3] docs/gpu: ci: update flake tests requirements Vignesh Raman
2024-09-27 7:45 ` Maxime Ripard
2024-09-27 14:35 ` Rodrigo Vivi [this message]
2024-09-30 7:31 ` 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=ZvbCzqvyeTI_j2cD@intel.com \
--to=rodrigo.vivi@intel.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=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=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.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;
as well as URLs for NNTP newsgroup(s).