Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Vignesh Raman <vignesh.raman@collabora.com>
Cc: <intel-gfx@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>, <jani.nikula@linux.intel.com>,
	<joonas.lahtinen@linux.intel.com>, <tursulin@ursulin.net>,
	<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: Re: drm-ci: flaky tests for i915 driver testing
Date: Tue, 10 Sep 2024 15:35:17 -0400	[thread overview]
Message-ID: <ZuCfdbFZiJ-1z4pU@intel.com> (raw)
In-Reply-To: <61f62c86-3e82-4eff-bd3c-8123fa0ca332@collabora.com>

On Tue, Sep 10, 2024 at 07:32:56AM +0530, Vignesh Raman wrote:
> Hi Maintainers,
> 
> On 12/07/24 11:22, Vignesh Raman wrote:
> > Hi Maintainers,
> > 
> > On 28/05/24 12:07, Vignesh Raman wrote:
> > > Hi Maintainers,
> > > 
> > > There are some flaky tests reported for i915 driver testing in
> > > drm-ci for the below boards.
> > > 
> > > *)
> > > # Board Name: asus-C523NA-A20057-coral
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > kms_fb_coherency@memset-crc
> > > 
> > > *)
> > > # Board Name: asus-C436FA-Flip-hatch
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > kms_plane_alpha_blend@constant-alpha-min
> > > 
> > > *)
> > > # Board Name: hp-x360-12b-ca0010nr-n4020-octopus
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > core_hotunplug@unplug-rescan
> > > kms_fb_coherency@memset-crc
> > > 
> > > *)
> > > # Board Name: hp-x360-14-G1-sona
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > prime_busy@hang
> > > 
> > > *)
> > > # Board Name: dell-latitude-5400-8665U-sarien
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > kms_pm_rpm@modeset-lpsp-stress
> > > 
> > > *)
> > > # Board Name: asus-C433TA-AJ0005-rammus
> > > # IGT Version: 1.28-g0df7b9b97
> > > # Linux Version: 6.9.0-rc7
> > > # Failure Rate: 50
> > > i915_hangman@engine-engine-error
> > > i915_hangman@gt-engine-hang
> > > kms_async_flips@crc
> > > kms_universal_plane@cursor-fb-leak
> > > 
> > > Will add these tests in,
> > > drivers/gpu/drm/ci/xfails/i915-amly-flakes.txt
> > > drivers/gpu/drm/ci/xfails/i915-apl-flakes.txt
> > > drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt
> > > drivers/gpu/drm/ci/xfails/i915-glk-flakes.txt
> > > drivers/gpu/drm/ci/xfails/i915-kbl-flakes.txt
> > > drivers/gpu/drm/ci/xfails/i915-whl-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.
> > 
> > There are some flaky tests reported for i915 driver testing in drm-ci
> > with the recent IGT uprev in drm-ci (https://gitlab.freedesktop.org/drm/misc/kernel/-/commit/0e7f4e6a20d550252c4f355d5a303b1d9c8ff052)
> > 
> > *)
> > # Board Name: asus-C433TA-AJ0005-rammus
> > # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/T/#u
> > # Failure Rate: 50
> > # IGT Version: 1.28-gf13702b8e
> > # Linux Version: 6.10.0-rc5
> > kms_sysfs_edid_timing
> > i915_hangman@engine-engine-hang
> > kms_pm_rpm@modeset-lpsp-stress
> > 
> > *)
> > # Board Name: asus-C436FA-Flip-hatch
> > # Bug Report: https://lore.kernel.org/intel-gfx/af4ca4df-a3ef-4943-bdbf-4c3af2c333af@collabora.com/T/#u
> > # Failure Rate: 50
> > # IGT Version: 1.28-gf13702b8e
> > # Linux Version: 6.10.0-rc5
> > kms_atomic_transition@plane-all-modeset-transition-internal-panels
> > 
> > The expectation files have been updated with these tests,
> > https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/drivers/gpu/drm/ci/xfails/i915-amly-flakes.txt
> > 
> > https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt
> 
> There are some flaky tests reported for i915 driver testing in drm-ci with
> the recent IGT uprev in drm-ci.
> 
> *)
> # Board Name: asus-C433TA-AJ0005-rammus
> # Failure Rate: 50
> # IGT Version: 1.28-ga73311079
> # Linux Version: 6.11.0-rc2
> kms_pm_rpm@drm-resources-equal
> 
> *)
> # Board Name: asus-C523NA-A20057-coral
> # Failure Rate: 100
> # IGT Version: 1.28-ga73311079
> # Linux Version: 6.11.0-rc2
> kms_universal_plane@cursor-fb-leak
> 
> *)
> # Board Name: asus-C436FA-Flip-hatch
> # Failure Rate: 100
> # IGT Version: 1.28-ga73311079
> # Linux Version: 6.11.0-rc2
> kms_plane_alpha_blend@constant-alpha-min
> 
> # Board Name: asus-C436FA-Flip-hatch
> # Failure Rate: 50
> # IGT Version: 1.28-ga73311079
> # Linux Version: 6.11.0-rc2
> kms_async_flips@crc
> 
> The expectation files have been updated with these tests,
> https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/drivers/gpu/drm/ci/xfails/i915-amly-flakes.txt
> 
> https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/drivers/gpu/drm/ci/xfails/i915-apl-flakes.txt
> 
> https://gitlab.freedesktop.org/drm/misc/kernel/-/blob/drm-misc-next/drivers/gpu/drm/ci/xfails/i915-cml-flakes.txt
> 
> Please could you have a look at these test results and let us know if you
> need more information. Thank you.

Hi Vignesh,

Where are exactly the logs? Any gitlab/issue reported for each case?

Getting this for instance:

# Board Name: asus-C436FA-Flip-hatch
# Failure Rate: 100
# IGT Version: 1.28-ga73311079
# Linux Version: 6.11.0-rc2
kms_plane_alpha_blend@constant-alpha-min

Looking to drm-tip CI:
https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=constant-alpha-min

it doesn't look like a 100% failure there.

Also, nothing special on 6.11.0-rc2 that could trigger that I'm afraid.

So, it would be good to have real individual bug reports [1] for each case
and some help on bisecting the commit level as well.

So, with more information we might get more attention to help these cases.
Otherwise I believe this list will just grow without a proper plan to move
back to the basic test list.

Thanks,
Rodrigo.

[1] - https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html

> 
> Regards,
> Vignesh

  reply	other threads:[~2024-09-10 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28  6:37 drm-ci: flaky tests for i915 driver testing Vignesh Raman
2024-07-12  5:52 ` Vignesh Raman
2024-09-10  2:02   ` Vignesh Raman
2024-09-10 19:35     ` Rodrigo Vivi [this message]
2024-09-11 11:53       ` 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=ZuCfdbFZiJ-1z4pU@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=guilherme.gallo@collabora.com \
    --cc=helen.koike@collabora.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=sergi.blanch.torne@collabora.com \
    --cc=tursulin@ursulin.net \
    --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