public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: Delegate exhaustive fault-injection to the idle runs
Date: Tue, 4 Feb 2020 14:53:21 +0200	[thread overview]
Message-ID: <e86bbe9a-a638-3fa4-9cb6-4eb1ba7f73d2@linux.intel.com> (raw)
In-Reply-To: <20200204114837.887623-1-chris@chris-wilson.co.uk>

On 04/02/2020 13:48, Chris Wilson wrote:
> i915_module_reload/fault-injection is valuable for its exhaustive trawl
> through (hopefully) every path that hits i915_probe_error, unfortunately
> such thoroughness comes at a cost. On kbl-guc, it takes almost 3minutes,
> and on tgl-y takes over 4 minutes, which is unacceptable for BAT, so leave
> it to the shards and idle runs to catch unusual errors on module load.
> 
> v2: remove blacklisting to allow module-reload in shards.
> 
> Tomi prefers not to have to manually create a runlist for the idle-runs,
> so let's take a risk by allowing the module-reload within the shards.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Martin Peres <martin.peres@linux.intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>

I think this is the right call! Thanks for doing it :)

Acked-by: Martin Peres <martin.peres@linux.intel.com>

Martin

> ---
>  tests/intel-ci/blacklist.txt          | 2 +-
>  tests/intel-ci/fast-feedback.testlist | 2 --
>  2 files changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index 723f24457..181c8cd5f 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -12,7 +12,7 @@ igt@drm_mm(@.*)?
>  # self-contained tests, leading to random
>  # failures in tests run afterwards.
>  ###############################################
> -igt@i915_module_load(@.*)?
> +#igt@i915_module_load(@.*)? # danger, danger; hope for taints!
>  igt@i915_pm_rpm@module-reload
>  igt@i915_pm_rpm@gem-execbuf-stress-extra-wait
>  ###############################################
> diff --git a/tests/intel-ci/fast-feedback.testlist b/tests/intel-ci/fast-feedback.testlist
> index 40d273c1d..467e11267 100644
> --- a/tests/intel-ci/fast-feedback.testlist
> +++ b/tests/intel-ci/fast-feedback.testlist
> @@ -172,6 +172,4 @@ igt@vgem_basic@sysfs
>  
>  igt@vgem_basic@unload
>  igt@i915_module_load@reload
> -igt@i915_module_load@reload-no-display
> -igt@i915_module_load@reload-with-fault-injection
>  igt@i915_pm_rpm@module-reload
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-02-04 12:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 11:48 [igt-dev] [PATCH i-g-t] intel-ci: Delegate exhaustive fault-injection to the idle runs Chris Wilson
2020-02-04 12:53 ` Martin Peres [this message]
2020-02-04 15:44 ` [igt-dev] ✗ GitLab.Pipeline: warning for intel-ci: Delegate exhaustive fault-injection to the idle runs (rev2) Patchwork
2020-02-04 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-06 15:21 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-12-04 17:48 [igt-dev] [PATCH i-g-t] intel-ci: Delegate exhaustive fault-injection to the idle runs Chris Wilson
2019-12-05 13:06 ` Petri Latvala

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=e86bbe9a-a638-3fa4-9cb6-4eb1ba7f73d2@linux.intel.com \
    --to=martin.peres@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    --cc=tomi.p.sarvela@intel.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