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:11:18 +0200 [thread overview]
Message-ID: <56a02b41-4c19-3adc-a380-b6be633b89f2@linux.intel.com> (raw)
In-Reply-To: <158221380406.8112.18309601206905414674@skylake-alporthouse-com>
On 2020-02-20 17:50, Chris Wilson wrote:
> Quoting Martin Peres (2020-02-20 15:32:09)
>> +###############################################################################
>> +# This tests modesetting-vs-wedged which is a useful thing to check, but it
>> +# seems like it mostly catches unrelated issues which are better caught by
>> +# other tests.
>> +#
>> +# - shard-skl: 0.5% (~1 minute)
>> +# - shard-kbl: 1% (~1 minute)
>> +# - shard-apl: 0.6% (~1 minute)
>> +# - shard-glk: 0.5% (~1 minute)
>> +# - shard-icl: 0.6% (~1.5 minutes)
>> +# - shard-tgl: 0.7% (~1.5 minutes)
>> +#
>> +# Data acquired on 2020-02-20 by Martin Peres
>> +###############################################################################
>> +igt@gem_eio@kms
>
> Hah. It caught novel issues, which have not been split out into separate
> regression tests.
>
> Making sure kms is robust is not a bad thing; you can easily speed this
> up by reducing the workload.
Thanks for your patch! I dropped this hunk :)
> -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:11 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
2020-02-20 15:50 ` Chris Wilson
2020-02-21 8:11 ` Martin Peres [this message]
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=56a02b41-4c19-3adc-a380-b6be633b89f2@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.