[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <58a9334d-26eb-4106-806a-59e5e728aed5@collabora.com>
Date: Tue, 24 Sep 2024 13:35:00 +0530
From: Vignesh Raman <vignesh.raman@...labora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: dri-devel@...ts.freedesktop.org, daniels@...labora.com,
helen.koike@...labora.com, airlied@...il.com, daniel@...ll.ch,
robdclark@...il.com, guilherme.gallo@...labora.com,
sergi.blanch.torne@...labora.com, deborah.brouwer@...labora.com,
mripard@...nel.org, rodrigo.vivi@...el.com,
linux-mediatek@...ts.infradead.org, linux-amlogic@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, amd-gfx@...ts.freedesktop.org,
linux-arm-msm@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
virtualization@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] docs/gpu: ci: update flake tests requirements
Hi Dmitry,
On 24/09/24 11:46, Dmitry Baryshkov wrote:
> On Tue, 24 Sept 2024 at 04:26, Vignesh Raman
> <vignesh.raman@...labora.com> wrote:
>>
>> Update the documentation to require linking to a relevant GitLab
>> issue for each new flake entry instead of an email report. Added
>> specific GitLab issue URLs for i915, xe and other drivers.
>>
>> Signed-off-by: Vignesh Raman <vignesh.raman@...labora.com>
>> ---
>> Documentation/gpu/automated_testing.rst | 15 ++++++++++-----
>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/gpu/automated_testing.rst b/Documentation/gpu/automated_testing.rst
>> index 2d5a28866afe..f73b8939dc3a 100644
>> --- a/Documentation/gpu/automated_testing.rst
>> +++ b/Documentation/gpu/automated_testing.rst
>> @@ -67,20 +67,25 @@ Lists the tests that for a given driver on a specific hardware revision are
>> 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.
>> +Each new flake entry must include a link to the relevant GitLab issue, 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: $GITLAB_ISSUE
>> # Board Name: broken-board.dtb
>> # Linux Version: 6.6-rc1
>> # IGT Version: 1.28-gd2af13d9f
>> # Failure Rate: 100
>> flaky-test
>>
>> +The GitLab issue must include the logs and the pipeline link. Use the appropriate
>> +link below to create an issue.
>> +https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/ for i915 drivers
>> +https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/ for xe drivers
>
> drm/msm for msm driver, please. Otherwise we can easily miss such issues.
Sure, will add it in v2. Thanks.
>
>> +https://gitlab.freedesktop.org/drm/misc/kernel/-/issues for other drivers
>> +
>> drivers/gpu/drm/ci/${DRIVER_NAME}-${HW_REVISION}-skips.txt
>> -----------------------------------------------------------
>>
>> --
>> 2.43.0
>>
>
>
Regards,
Vignesh
Powered by blists - more mailing lists