From: Petri Latvala via igt-dev <igt-dev@lists.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: Ignore performance-only pread/pwrite "tests"
Date: Fri, 15 Feb 2019 12:47:09 +0200 [thread overview]
Message-ID: <20190215104709.GX4038@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190215104158.15907-1-chris@chris-wilson.co.uk>
On Fri, Feb 15, 2019 at 10:41:58AM +0000, Chris Wilson wrote:
> We don't need to waste time running perf-only test cases when we are not
> manually checking results. ezbench is that away!
>
> References: https://bugs.freedesktop.org/show_bug.cgi?id=109640
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
Remove those subtests, put them in benchmarks/ along with an ezbench
integration script?
Acked-by: Petri Latvala <petri.latvala@intel.com>
> tests/intel-ci/blacklist.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
> index 0e6beeae4..2bdc0b25b 100644
> --- a/tests/intel-ci/blacklist.txt
> +++ b/tests/intel-ci/blacklist.txt
> @@ -50,6 +50,7 @@ igt@gem_mmap@.*(swap|huge).*
> igt@gem_mocs_settings@.*(suspend|hibernate).*
> igt@gem_pin(@.*)?
> igt@gem_pread_after_blit(@.*)?
> +igt@gem_pwrite_pread@.*performance.*
> igt@gem_read_read_speed(@.*)?
> igt@gem_reloc_overflow(@.*)?
> igt@gem_reloc_vs_gpu(@.*)?
> --
> 2.20.1
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-15 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 10:41 [igt-dev] [PATCH i-g-t] intel-ci: Ignore performance-only pread/pwrite "tests" Chris Wilson
2019-02-15 10:47 ` Petri Latvala via igt-dev [this message]
2019-02-15 10:52 ` Chris Wilson
2019-02-15 15:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
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=20190215104709.GX4038@platvala-desk.ger.corp.intel.com \
--to=igt-dev@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@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