public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: Delegate exhaustive fault-injection to the idle runs
Date: Thu, 5 Dec 2019 15:06:13 +0200	[thread overview]
Message-ID: <20191205130613.GD25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20191204174817.3877367-1-chris@chris-wilson.co.uk>

On Wed, Dec 04, 2019 at 05:48:17PM +0000, 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,
> which is unacceptable for BAT, so leave it to the shards and idle runs
> to catch unusual errors on module load.


Pointed this out in IRC, but for the benefit of the mailing list:
i915_module_load is blacklisted on shards so this would leave these
tests only for the idle runs.


-- 
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-12-05 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-04 20:07 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-12-05 13:06 ` Petri Latvala [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-04 11:48 [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-02-04 12:53 ` Martin Peres

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=20191205130613.GD25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    /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