From: Helen Mae Koike Fornazier <helen.koike@collabora.com>
To: "Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Vignesh Raman" <vignesh.raman@collabora.com>
Cc: "Rob Clark" <robdclark@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Sean Paul" <sean@poorly.run>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-arm-msm" <linux-arm-msm@vger.kernel.org>,
"dri-devel" <dri-devel@lists.freedesktop.org>,
"freedreno" <freedreno@lists.freedesktop.org>
Subject: Re: [PATCH] drm/ci: add kms_cursor_legacy@torture-bo to apq8016 flakes
Date: Wed, 04 Dec 2024 17:33:02 -0300 [thread overview]
Message-ID: <19393604e18.f9b6fe7d298023.1937039548910081216@collabora.com> (raw)
In-Reply-To: <20a3955e-3d10-47c5-8e68-d70342805010@quicinc.com>
---- On Wed, 04 Dec 2024 16:21:26 -0300 Abhinav Kumar wrote ---
> Hi Helen
>
> On 12/4/2024 11:14 AM, Helen Mae Koike Fornazier wrote:
> > Hi Abhinav,
> >
> > Thanks for your patch.
> >
> >
> >
> > ---- On Wed, 04 Dec 2024 15:55:17 -0300 Abhinav Kumar wrote ---
> >
> > > From the jobs [1] and [2] of pipeline [3], its clear that
> > > kms_cursor_legacy@torture-bo is most certainly a flake and
> > > not a fail for apq8016. Mark the test accordingly to match the results.
> > >
> > > [1] : https://gitlab.freedesktop.org/drm/msm/-/jobs/67676481
> > > [2] : https://gitlab.freedesktop.org/drm/msm/-/jobs/67677430
> > > [3]: https://gitlab.freedesktop.org/drm/msm/-/pipelines/1322770
> > >
> > > Signed-off-by: Abhinav Kumar quic_abhinavk@quicinc.com>
> > > ---
> > > drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt | 5 +++++
> > > 1 file changed, 5 insertions(+)
> > >
> > > diff --git a/drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt b/drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt
> > > new file mode 100644
> > > index 000000000000..18639853f18f
> > > --- /dev/null
> > > +++ b/drivers/gpu/drm/ci/xfails/msm-apq8016-flakes.txt
> > > @@ -0,0 +1,5 @@
> > > +# Board Name: msm-apq8016-db410c
> > > +# Failure Rate: 100
> >
> > Is failure rate is 100%, isn't it a fail than?
> > (I know we have other cases with Failure Rate: 100, maybe we should fix them as well)
> >
>
> Maybe I misunderstood the meaning of "Failure rate" for a flake.
>
> I interpreted this as this test being flaky 100% of the time :)
Ah right, I see, inside deqp-runner (that auto-retries).
I'd like to hear Vignesh's opinion on this.
(In any case, we probably should document this better)
Regards,
Helen
>
> Out of the 3 runs of the test, it passed 2/3 times and failed 1/3.
>
> So its fail % actually is 33.33% in that case.
>
> I think I saw a Failure rate of 100% on msm-sm8350-hdk-flakes.txt and
> mistook that as the rate at which flakes are seen.
>
> Let me fix this up as 33%
>
> > Regards,
> > Helen
> >
> > > +# IGT Version: 1.28-ga73311079
> > > +# Linux Version: 6.12.0-rc2
> > > +kms_cursor_legacy@torture-bo
> > >
> > > ---
> > > base-commit: 798bb342e0416d846cf67f4725a3428f39bfb96b
> > > change-id: 20241204-cursor_tor_skip-9d128dd62c4f
> > >
> > > Best regards,
> > > --
> > > Abhinav Kumar quic_abhinavk@quicinc.com>
> > >
> > >
> >
>
next prev parent reply other threads:[~2024-12-04 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 18:55 Abhinav Kumar
2024-12-04 19:14 ` Helen Mae Koike Fornazier
2024-12-04 19:21 ` Abhinav Kumar
2024-12-04 20:33 ` Helen Mae Koike Fornazier [this message]
2024-12-11 20:18 ` Abhinav Kumar
2024-12-12 5:10 ` Vignesh Raman
2024-12-13 19:39 ` Abhinav Kumar
2024-12-16 5:45 ` Vignesh Raman
2024-12-16 6:09 ` Abhinav Kumar
2024-12-18 13:57 ` 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=19393604e18.f9b6fe7d298023.1937039548910081216@collabora.com \
--to=helen.koike@collabora.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vignesh.raman@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®