All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 8/8] i915/gem_exec_basic: Use dynamic subtests
Date: Mon, 11 Nov 2019 12:06:13 +0200	[thread overview]
Message-ID: <20191111100613.GM25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <6c376ea8-1c33-3d95-37a8-f2e5f0cb4722@linux.intel.com>

On Fri, Nov 08, 2019 at 04:33:24PM +0000, Tvrtko Ursulin wrote:
> 
> On 08/11/2019 16:31, Tvrtko Ursulin wrote:
> > 
> > On 24/10/2019 12:05, Petri Latvala wrote:
> > > Instead of generating a subtest for each engine in a static list,
> > > convert to dynamic subtests, with one dynamic subtest per actually
> > > present physical engine.
> > > 
> > > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> > > ---
> > >   tests/i915/gem_exec_basic.c | 26 +++++++++++++++++++-------
> > >   1 file changed, 19 insertions(+), 7 deletions(-)
> > > 
> > > diff --git a/tests/i915/gem_exec_basic.c b/tests/i915/gem_exec_basic.c
> > > index 1287860b..b2d6ddc2 100644
> > > --- a/tests/i915/gem_exec_basic.c
> > > +++ b/tests/i915/gem_exec_basic.c
> > > @@ -159,13 +159,25 @@ igt_main
> > >       igt_subtest("gtt-all")
> > >           gtt_all(fd);
> > > -    __for_each_physical_engine(fd, e) {
> > > -        igt_subtest_f("basic-%s", e->name)
> > > -            noop(fd, e->flags);
> > > -        igt_subtest_f("readonly-%s", e->name)
> > > -            readonly(fd, e->flags);
> > > -        igt_subtest_f("gtt-%s", e->name)
> > > -            gtt(fd, e->flags);
> > > +    igt_subtest_with_dynamic_subsubtests("basic") {
> > 
> > Bikeshed on the name maybe, since "subsub" reads a bit funny.
> > 
> > igt_dynamic_subtest_group ?
> 
> Assuming at least it can both nest under igt_subtest_group and not nest ie.
> be at top-level? Do we need a nested version even?

It's a brother of igt_subtest, not a brother of
igt_subtest_group. igt_subtest_with_dynamic_subsubtests() is, like
igt_subtest(),

 * execution entry with --run-subtest
 * enumerable with --list-subtests
 * a block where you can touch the system inside it
 * nests inside an igt_subtest_group and automatically produces a
   'SKIP' if a fixture in that group triggered an igt_require

I'm all for bikeshedding on the name, but I want the closer
association to igt_subtest to show. I like none of the names discussed
so far all around the mailing list, I hate this current one the least
so far. If it's all right, I'd like to land the series and start
converting tests while the naming bikeshed (again, very welcome
bikeshed) goes on simultaneously. It's a matter of a quick sed
magickry later.


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

  reply	other threads:[~2019-11-11 10:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 11:05 [igt-dev] [PATCH i-g-t 0/8] Dynamic subtests, v3 Petri Latvala
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 1/8] lib: Introduce dynamic subsubtests Petri Latvala
2019-10-25  7:49   ` Arkadiusz Hiler
2019-11-11 10:11   ` [igt-dev] [PATCH i-g-t v4 " Petri Latvala
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 2/8] lib/tests: Unit tests for dynamic subtests Petri Latvala
2019-10-25  8:05   ` Arkadiusz Hiler
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 3/8] lib/tests: Test that igt_describe works with " Petri Latvala
2019-10-25  9:35   ` Arkadiusz Hiler
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 4/8] runner: Parse dynamic subtest outputs and results Petri Latvala
2019-10-25 11:03   ` Arkadiusz Hiler
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 5/8] runner/json_tests: Test dynamic subtests Petri Latvala
2019-10-25 11:22   ` Arkadiusz Hiler
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 6/8] kms_plane_cursor: Use " Petri Latvala
2019-11-08 16:15   ` Katarzyna Dec
2019-11-14 12:03   ` Petri Latvala
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 7/8] perf_pmu: " Petri Latvala
2019-11-08 16:13   ` Katarzyna Dec
2019-11-08 16:27     ` Tvrtko Ursulin
2019-10-24 11:05 ` [igt-dev] [PATCH i-g-t 8/8] i915/gem_exec_basic: " Petri Latvala
2019-11-05  9:24   ` Katarzyna Dec
2019-11-08 16:31   ` Tvrtko Ursulin
2019-11-08 16:33     ` Tvrtko Ursulin
2019-11-11 10:06       ` Petri Latvala [this message]
2019-11-11 10:36         ` Tvrtko Ursulin
2019-10-24 13:50 ` [igt-dev] ✗ GitLab.Pipeline: warning for Dynamic subtests (rev3) Patchwork
2019-10-24 13:58 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-10-25 19:08 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-11-11 11:22 ` [igt-dev] ✓ Fi.CI.BAT: success for Dynamic subtests (rev4) Patchwork
2019-11-11 13:51 ` [igt-dev] ✗ GitLab.Pipeline: failure " Patchwork
2019-11-11 20:15 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=20191111100613.GM25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.