From: Tvrtko Ursulin <tursulin@ursulin.net>
To: Intel-gfx@lists.freedesktop.org
Subject: [RFC i-g-t 2/2] extended.testlist: Remove some test-subtest combinations
Date: Fri, 16 Jun 2017 11:55:30 +0100 [thread overview]
Message-ID: <20170616105530.22302-2-tvrtko.ursulin@linux.intel.com> (raw)
In-Reply-To: <20170616105530.22302-1-tvrtko.ursulin@linux.intel.com>
From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
For tests with attempt to hit races and such by running for
relatively long time, it seems that it might be possible to get
by only testing some subtest-engine combinations as long as in
total we still exercise all engines per test.
More precisely, I think that if we view our engines as fast
(!rcs) and a little less fast (others), we group the race
hitting tests in those two camps, we keep the same coverage
by running each subtest against each engine group.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
---
tests/intel-ci/extended.testlist | 44 ----------------------------------------
1 file changed, 44 deletions(-)
diff --git a/tests/intel-ci/extended.testlist b/tests/intel-ci/extended.testlist
index e0926ff09bcd..246a14f6e501 100644
--- a/tests/intel-ci/extended.testlist
+++ b/tests/intel-ci/extended.testlist
@@ -73,11 +73,7 @@ igt@gem_pwrite@huge-gtt-fbr
igt@gem_pwrite@huge-gtt-forwards
igt@gem_pwrite@huge-gtt-random
igt@gem_ringfill@blt-bomb
-igt@gem_ringfill@bsd-bomb
-igt@gem_ringfill@bsd1-bomb
-igt@gem_ringfill@bsd2-bomb
igt@gem_ringfill@render-bomb
-igt@gem_ringfill@vebox-bomb
igt@gem_userptr_blits@stress-mm
igt@gem_userptr_blits@stress-mm-invalidate-close
igt@gem_userptr_blits@stress-mm-invalidate-close-overlap
@@ -1654,30 +1650,14 @@ igt@gem_ring_sync_copy@sync-render-blitter-read-write
igt@gem_ring_sync_copy@sync-render-blitter-write-read
igt@gem_ring_sync_copy@sync-render-blitter-write-write
igt@gem_ring_sync_loop
-igt@gem_ringfill@blt
-igt@gem_ringfill@blt-child
igt@gem_ringfill@blt-interruptible
-igt@gem_ringfill@blt-s3
igt@gem_ringfill@bsd
-igt@gem_ringfill@bsd-child
-igt@gem_ringfill@bsd-interruptible
igt@gem_ringfill@bsd-s3
-igt@gem_ringfill@bsd1
-igt@gem_ringfill@bsd1-child
-igt@gem_ringfill@bsd1-interruptible
-igt@gem_ringfill@bsd1-s3
-igt@gem_ringfill@bsd2
-igt@gem_ringfill@bsd2-child
-igt@gem_ringfill@bsd2-interruptible
-igt@gem_ringfill@bsd2-s3
igt@gem_ringfill@render
igt@gem_ringfill@render-child
igt@gem_ringfill@render-interruptible
igt@gem_ringfill@render-s3
-igt@gem_ringfill@vebox
igt@gem_ringfill@vebox-child
-igt@gem_ringfill@vebox-interruptible
-igt@gem_ringfill@vebox-s3
igt@gem_set_tiling_vs_blt@tiled-to-tiled
igt@gem_set_tiling_vs_blt@tiled-to-untiled
igt@gem_set_tiling_vs_blt@untiled-to-tiled
@@ -1711,35 +1691,17 @@ igt@gem_storedw_batches_loop@normal
igt@gem_storedw_batches_loop@secure-dispatch
igt@gem_storedw_batches_loop@uncached-mapping
igt@gem_storedw_loop@long-blt
-igt@gem_storedw_loop@long-bsd
-igt@gem_storedw_loop@long-bsd1
-igt@gem_storedw_loop@long-bsd2
igt@gem_storedw_loop@long-render
igt@gem_storedw_loop@long-vebox
-igt@gem_storedw_loop@short-blt
igt@gem_storedw_loop@short-bsd
-igt@gem_storedw_loop@short-bsd1
-igt@gem_storedw_loop@short-bsd2
igt@gem_storedw_loop@short-render
igt@gem_storedw_loop@short-vebox
igt@gem_sync@blt
-igt@gem_sync@bsd
-igt@gem_sync@bsd1
-igt@gem_sync@bsd2
-igt@gem_sync@many-blt
igt@gem_sync@many-bsd
-igt@gem_sync@many-bsd1
-igt@gem_sync@many-bsd2
igt@gem_sync@many-render
-igt@gem_sync@many-vebox
igt@gem_sync@render
-igt@gem_sync@store-blt
-igt@gem_sync@store-bsd
-igt@gem_sync@store-bsd1
-igt@gem_sync@store-bsd2
igt@gem_sync@store-render
igt@gem_sync@store-vebox
-igt@gem_sync@vebox
igt@gem_threaded_access_tiled
igt@gem_tiled_blits@interruptible
igt@gem_tiled_blits@normal
@@ -1786,17 +1748,11 @@ igt@gem_userptr_blits@unsync-unmap-after-close
igt@gem_userptr_blits@unsync-unmap-cycles
igt@gem_userptr_blits@usage-restrictions
igt@gem_wait@busy-blt
-igt@gem_wait@busy-bsd
-igt@gem_wait@busy-bsd1
-igt@gem_wait@busy-bsd2
igt@gem_wait@busy-render
igt@gem_wait@busy-vebox
igt@gem_wait@invalid-buf
igt@gem_wait@invalid-flags
-igt@gem_wait@wait-blt
igt@gem_wait@wait-bsd
-igt@gem_wait@wait-bsd1
-igt@gem_wait@wait-bsd2
igt@gem_wait@wait-render
igt@gem_wait@wait-vebox
igt@gem_workarounds@reset
--
2.9.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-16 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 10:55 [RFC i-g-t 1/2] extended.testlist: Remove default and render engine test duplicates Tvrtko Ursulin
2017-06-16 10:55 ` Tvrtko Ursulin [this message]
2017-06-16 11:01 ` [RFC i-g-t 2/2] extended.testlist: Remove some test-subtest combinations Chris Wilson
2017-06-16 16:00 ` [RFC i-g-t 1/2] extended.testlist: Remove default and render engine test duplicates Chris Wilson
2017-06-22 9:54 ` Daniel Vetter
2017-06-22 10:45 ` Tvrtko Ursulin
2017-06-23 11:14 ` Daniel Vetter
2017-06-23 11:21 ` Chris Wilson
2017-06-26 16:05 ` Daniel Vetter
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=20170616105530.22302-2-tvrtko.ursulin@linux.intel.com \
--to=tursulin@ursulin.net \
--cc=Intel-gfx@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.