All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time
Date: Mon, 7 Jan 2019 11:12:30 +0000	[thread overview]
Message-ID: <ee86d31e-c39e-e854-1a40-a58cf40545d4@linux.intel.com> (raw)
In-Reply-To: <20190107110125.GW17124@platvala-desk.ger.corp.intel.com>


On 07/01/2019 11:01, Petri Latvala wrote:
> On Fri, Jan 04, 2019 at 03:37:09PM +0000, Tvrtko Ursulin wrote:
>> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
>> index 73d127603d28..d76a4b3b1c71 100644
>> --- a/tests/intel-ci/blacklist.txt
>> +++ b/tests/intel-ci/blacklist.txt
>> @@ -60,6 +60,7 @@ igt@gem_ring_sync_copy(@.*)?
>>   igt@gem_ring_sync_loop(@.*)?
>>   igt@gem_seqno_wrap(@.*)?
>>   igt@gem_shrink@(?!reclaim$).*
>> +igt@gem_shrink@(?!reclaims-and-oom).*
>>   igt@gem_softpin@.*(hang|S4).*
>>   igt@gem_spin_batch(@.*)?
>>   igt@gem_stolen@.*hibernate.*
> 
> 
> In case you didn't notice: The first gem_shrink line removes the
> reclaims-and-oom* subtests, and the second line (the one you added)
> then removes the 'reclaim' subtest, resulting in all gem_shrink
> subtests blacklisted.

No I haven't thank you. Interestingly the reclaim subtest still did run. 
Okay, but in essence should this work then:

   igt@gem_shrink@(?!reclaim).*

To blacklist everything apart from reclaims and reclaims-and-oom.* subtests?

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: igt-dev@lists.freedesktop.org, Intel-gfx@lists.freedesktop.org,
	Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time
Date: Mon, 7 Jan 2019 11:12:30 +0000	[thread overview]
Message-ID: <ee86d31e-c39e-e854-1a40-a58cf40545d4@linux.intel.com> (raw)
In-Reply-To: <20190107110125.GW17124@platvala-desk.ger.corp.intel.com>


On 07/01/2019 11:01, Petri Latvala wrote:
> On Fri, Jan 04, 2019 at 03:37:09PM +0000, Tvrtko Ursulin wrote:
>> diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt
>> index 73d127603d28..d76a4b3b1c71 100644
>> --- a/tests/intel-ci/blacklist.txt
>> +++ b/tests/intel-ci/blacklist.txt
>> @@ -60,6 +60,7 @@ igt@gem_ring_sync_copy(@.*)?
>>   igt@gem_ring_sync_loop(@.*)?
>>   igt@gem_seqno_wrap(@.*)?
>>   igt@gem_shrink@(?!reclaim$).*
>> +igt@gem_shrink@(?!reclaims-and-oom).*
>>   igt@gem_softpin@.*(hang|S4).*
>>   igt@gem_spin_batch(@.*)?
>>   igt@gem_stolen@.*hibernate.*
> 
> 
> In case you didn't notice: The first gem_shrink line removes the
> reclaims-and-oom* subtests, and the second line (the one you added)
> then removes the 'reclaim' subtest, resulting in all gem_shrink
> subtests blacklisted.

No I haven't thank you. Interestingly the reclaim subtest still did run. 
Okay, but in essence should this work then:

   igt@gem_shrink@(?!reclaim).*

To blacklist everything apart from reclaims and reclaims-and-oom.* subtests?

Regards,

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

  reply	other threads:[~2019-01-07 11:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 15:37 [PATCH i-g-t] tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time Tvrtko Ursulin
2019-01-04 15:37 ` [Intel-gfx] " Tvrtko Ursulin
2019-01-04 16:05 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-04 16:57 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-01-07 11:01 ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2019-01-07 11:01   ` Petri Latvala
2019-01-07 11:12   ` Tvrtko Ursulin [this message]
2019-01-07 11:12     ` Tvrtko Ursulin
2019-01-07 11:28     ` Petri Latvala
2019-01-07 11:28       ` Petri Latvala
2019-01-07 17:33       ` Tvrtko Ursulin
2019-01-07 17:33         ` Tvrtko Ursulin
2019-01-07 12:27 ` Michał Winiarski
2019-01-07 12:27   ` Michał Winiarski
2019-01-07 12:31   ` Chris Wilson
2019-01-07 12:31     ` Chris Wilson
2019-01-07 12:52     ` Tvrtko Ursulin
2019-01-07 12:52       ` Tvrtko Ursulin
2019-01-07 12:56       ` Chris Wilson
2019-01-07 12:56         ` Chris Wilson
2019-01-07 17:36 ` [PATCH i-g-t v2] " Tvrtko Ursulin
2019-01-07 17:36   ` [igt-dev] " Tvrtko Ursulin
2019-01-07 18:22   ` [PATCH i-g-t v3] " Tvrtko Ursulin
2019-01-07 18:22     ` [igt-dev] " Tvrtko Ursulin
2019-01-08 10:57     ` Chris Wilson
2019-01-08 10:57       ` [igt-dev] [Intel-gfx] " Chris Wilson
2019-01-07 18:00 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev2) Patchwork
2019-01-07 18:25   ` Tvrtko Ursulin
2019-01-07 20:53     ` Chris Wilson
2019-01-07 21:43       ` Chris Wilson
2019-01-07 19:24 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/gem_shrink: Exercise OOM and other routes to shrinking in reasonable time (rev3) Patchwork
2019-01-07 22:15 ` [igt-dev] ✓ Fi.CI.IGT: " 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=ee86d31e-c39e-e854-1a40-a58cf40545d4@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@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 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.