From: Vignesh Raman <vignesh.raman@collabora.com>
To: freedreno@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org
Cc: robdclark@gmail.com, quic_abhinavk@quicinc.com,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
sean@poorly.run, marijn.suijten@somainline.org,
airlied@gmail.com, daniel@ffwll.ch,
Daniel Stone <daniels@collabora.com>,
Helen Mae Koike Fornazier <helen.koike@collabora.com>,
Sergi Blanch Torne <sergi.blanch.torne@collabora.com>,
Guilherme Alcarde Gallo <guilherme.gallo@collabora.com>
Subject: drm-ci: flaky tests for msm driver testing
Date: Tue, 28 May 2024 11:39:23 +0530 [thread overview]
Message-ID: <661483c8-ad82-400d-bcd8-e94986d20d7d@collabora.com> (raw)
Hi Maintainers,
There are some flaky tests reported for msm driver testing in drm-ci for
the below boards.
*)
# Board Name: apq8096-db820c
# IGT Version: 1.28-g0df7b9b97
# Linux Version: 6.9.0-rc7
# Failure Rate: 50
dumb_buffer@create-clear
*)
# Board Name: sc7180-trogdor-kingoftown
# IGT Version: 1.28-g0df7b9b97
# Linux Version: 6.9.0-rc7
# Failure Rate: 50
msm_mapping@shadow
msm_shrink@copy-gpu-oom-32
msm_shrink@copy-gpu-oom-8
*)
# Board Name: sc7180-trogdor-lazor-limozeen-nots-r5
# IGT Version: 1.28-g0df7b9b97
# Linux Version: 6.9.0-rc7
# Failure Rate: 50
msm_mapping@shadow
*)
# Board Name: sdm845-cheza-r3
# IGT Version: 1.28-g0df7b9b97
# Linux Version: 6.9.0-rc7
# Failure Rate: 50
kms_cursor_legacy@basic-flip-after-cursor-atomic
kms_cursor_legacy@basic-flip-after-cursor-legacy
kms_cursor_legacy@basic-flip-after-cursor-varying-size
kms_cursor_legacy@basic-flip-before-cursor-varying-size
kms_cursor_legacy@flip-vs-cursor-atomic-transitions
kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size
kms_cursor_legacy@flip-vs-cursor-varying-size
kms_cursor_legacy@short-flip-after-cursor-atomic-transitions
kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size
kms_cursor_legacy@short-flip-after-cursor-toggle
kms_cursor_legacy@short-flip-before-cursor-atomic-transitions
kms_cursor_legacy@short-flip-before-cursor-atomic-transitions-varying-size
msm_shrink@copy-gpu-32
msm_shrink@copy-gpu-oom-32
Will add these tests in,
drivers/gpu/drm/ci/xfails/msm-apq8096-flakes.txt
drivers/gpu/drm/ci/xfails/msm-sc7180-trogdor-kingoftown-flakes.txt
drivers/gpu/drm/ci/xfails/msm-sc7180-trogdor-lazor-limozeen-flakes.txt
drivers/gpu/drm/ci/xfails/msm-sdm845-flakes.txt
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Documentation/gpu/automated_testing.rst#n70)
Please could you have a look at these test results and let us know if
you need more information. Thank you.
Regards,
Vignesh
next reply other threads:[~2024-05-28 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 6:09 Vignesh Raman [this message]
2024-07-12 6:05 ` drm-ci: flaky tests for msm driver testing Vignesh Raman
2024-09-10 3:18 ` Vignesh Raman
2024-09-10 14:45 ` Dmitry Baryshkov
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=661483c8-ad82-400d-bcd8-e94986d20d7d@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=freedreno@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.koike@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--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