From: Martin Peres <martin.peres@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] intel-ci: add a pre-merge blacklist to reduce the testing queue
Date: Fri, 21 Feb 2020 10:10:41 +0200 [thread overview]
Message-ID: <46136608-3e86-6ac7-d9af-86c5c58d88f5@linux.intel.com> (raw)
In-Reply-To: <158221356538.8112.10760355305068621449@skylake-alporthouse-com>
On 2020-02-20 17:46, Chris Wilson wrote:
> Quoting Martin Peres (2020-02-20 15:32:09)
>> +###############################################################################
>> +# Modern userspace does not depend on the GTT anymore, so let's drop the
>> +# slowest tests from pre-merge testing:
>> +#
>> +# - shard-skl: 2.7% (~6.5 minutes)
>> +# - shard-kbl: 2% (~2.5 minutes)
>> +# - shard-apl: 4.7% (~8.5 minutes)
>> +# - shard-glk: 3.5% (~8 minutes)
>> +# - shard-icl: 4.2% (~8.5 minutes)
>> +# - shard-tgl: 2.5% (~4.5 minutes)
>> +#
>> +# Data acquired on 2020-02-20 by Martin Peres
>> +###############################################################################
>> +igt@gem_fence_thrash@bo-write-verify-threaded-[xy]
>> +igt@gem_tiled_(wc|(|blits|fence_blits)@(normal|interruptible))
>
> So where's the pre-merge regression testing then?
I assume that the problem are the tests' assumptions, so if someone
wants to change them, they can just remove the tests from the blacklist.
> Just speed the tests up.
I'll be looking forward to reviewing them, in the mean time, it will be
post-merge testing only for these. We have plenty of other GTT tests
that are kept.
Martin
> -Chris
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-02-21 8:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:32 [igt-dev] [PATCH i-g-t] intel-ci: add a pre-merge blacklist to reduce the testing queue Martin Peres
2020-02-20 15:39 ` Chris Wilson
2020-02-20 15:43 ` Chris Wilson
2020-02-20 17:41 ` Chris Wilson
2020-02-20 15:44 ` Chris Wilson
2020-02-20 16:19 ` Peres, Martin
2020-02-20 15:46 ` Chris Wilson
2020-02-21 8:10 ` Martin Peres [this message]
2020-02-20 15:50 ` Chris Wilson
2020-02-21 8:11 ` Martin Peres
2020-02-20 15:52 ` Chris Wilson
2020-02-21 8:11 ` Martin Peres
2020-02-20 15:58 ` Chris Wilson
2020-02-20 16:29 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-21 9:00 ` [igt-dev] [PATCH i-g-t v2] " Martin Peres
2020-02-21 10:11 ` Petri Latvala
2020-02-21 10:43 ` Chris Wilson
2020-02-21 9:42 ` [igt-dev] ✓ Fi.CI.BAT: success for intel-ci: add a pre-merge blacklist to reduce the testing queue (rev2) Patchwork
2020-02-21 10:20 ` [igt-dev] [PATCH i-g-t] intel-ci: add a pre-merge blacklist to reduce the testing queue Petri Latvala
2020-02-21 11:27 ` Petri Latvala
2020-02-22 21:32 ` [igt-dev] ✓ Fi.CI.IGT: success 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=46136608-3e86-6ac7-d9af-86c5c58d88f5@linux.intel.com \
--to=martin.peres@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.