From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t v2] tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic
Date: Thu, 30 Jan 2020 20:59:45 +0000 [thread overview]
Message-ID: <09861f70-4ce1-fcc0-7c2f-5c1cb31f116c@linux.intel.com> (raw)
In-Reply-To: <158041781735.18112.13290397906308346272@skylake-alporthouse-com>
On 30/01/2020 20:56, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2020-01-30 20:52:56)
>> @@ -772,91 +787,64 @@ igt_main
>> igt_allow_hang(i915, 0, 0);
>> }
>>
>> - igt_subtest("idempotent")
>> - test_idempotent(i915);
>> -
>> - igt_subtest("clone")
>> - test_clone(i915);
>> -
>> - igt_subtest("file")
>> - test_nonpersistent_file(i915);
>> -
>> - igt_subtest("process")
>> - test_process(i915);
>> -
>> - igt_subtest("processes")
>> - test_processes(i915);
>> -
>> - igt_subtest("hostile")
>> - test_nohangcheck_hostile(i915);
>> - igt_subtest("hang")
>> - test_nohangcheck_hang(i915);
>
> Could we keep these outside of the engine subtest groups?
> I'd like to keep them distinct as they aren't written with verifying
> engines per se, but the general context parameter.
>
> There should be per-engine equivalents to the above already where
> appropriate.
Depends how you look at it, I envisioned two subgroups as telling me
when the default context is really default and when it has been
configured with an engine map.
Oh right contexts... okay I need a third subgroup.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-30 20:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 20:41 [igt-dev] [PATCH i-g-t] tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic Tvrtko Ursulin
2020-01-30 20:44 ` Tvrtko Ursulin
2020-01-30 20:50 ` [igt-dev] [Intel-gfx] " Chris Wilson
2020-01-30 20:47 ` Chris Wilson
2020-01-30 20:56 ` Tvrtko Ursulin
2020-01-30 21:17 ` Chris Wilson
2020-01-30 20:52 ` [Intel-gfx] [PATCH i-g-t v2] " Tvrtko Ursulin
2020-01-30 20:56 ` [igt-dev] " Chris Wilson
2020-01-30 20:59 ` Tvrtko Ursulin [this message]
2020-01-30 20:56 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-01-30 21:01 ` [igt-dev] [PATCH i-g-t v3] " Tvrtko Ursulin
2020-01-30 21:07 ` Chris Wilson
2020-01-30 21:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2020-01-30 21:26 ` [igt-dev] ✗ GitLab.Pipeline: failure for tests/i915/gem_ctx_persistence: Convert engine subtests to dynamic (rev3) Patchwork
2020-01-30 21:33 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-02 12:49 ` [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=09861f70-4ce1-fcc0-7c2f-5c1cb31f116c@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=krishnaiah.bommu@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