public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 0/6] Dynamic subtests
Date: Fri, 2 Aug 2019 16:23:18 +0200	[thread overview]
Message-ID: <20190802142318.GO7444@phenom.ffwll.local> (raw)
In-Reply-To: <20190722123233.GB3698@platvala-desk.ger.corp.intel.com>

On Mon, Jul 22, 2019 at 03:32:33PM +0300, Petri Latvala wrote:
> On Fri, Jun 21, 2019 at 10:26:31AM +0100, Tvrtko Ursulin wrote:
> > I am confused by all this. Could we then achieve the same result by just
> > adding the ability to hide subtests from test enumeration?
> > 
> > igt_subtest_group {
> > 	igt_subtest("a");
> > }
> > 
> > igt_dynamic_subtest_group("group") {
> > 	igt_subtest("b");
> > }
> > 
> > # ./test --list-subtests
> > a
> > group
> > 
> > # .test --list-all-subtests
> > a
> > group-b
> > 
> > # ./test --r group
> > PASS
> > 
> > # ./test --r group-b
> > PASS
> > 
> > Would the above satisfy CI requirements? Sounds like it would be easier to
> > implement wrt needed code base changes in individual tests and possibly the
> > IGT core code would not be difficult either? Just needs to track in what
> > kind of subgroup it is to decide what to do when listing/running tests.
> 
> 
> With sufficient fiddling of names, this is exactly what this series does.
> 
> 
> igt_subtest_group {
> 	igt_subtest("a");
> }
> 
> igt_dynamic_subtest_container("group") {
> 	igt_dynamic_subtest("b");
> }
> 
> # ./test --list-subtests
> a
> group
> 
> # .test --list-all-subtests
> error: nope
> 
> # ./test --r group
> Dynamic "b": PASS
> PASS
> 
> # ./test --r group --dynamic-subtest b
> Dynamic "b": PASS
> PASS
> 
> 
> 
> The listing of dynamic subtests is not implemented as that is
> definitely not trivial.

I think trying to list dynamic subtests without running them defeats the
entire point here. At least it would get really tricky to tell "hw/driver
acccess necessary to enumerate tests" from "hw/driver access that actually
tests something". E.g. with atomic TEST_ONLY you might have to actually
construct all the possible configs to figure out which ones are supported.
-Daniel

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

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-08-02 14:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 11:51 [igt-dev] [PATCH i-g-t 0/6] Dynamic subtests Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 1/6] lib: Introduce dynamic subtests Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 2/6] lib/tests: Unit tests for " Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 3/6] runner/resultgen: Refactor output parsing Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 4/6] runner/json_tests: Adapt to better " Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 5/6] runner: Parse dynamic subtest outputs and results Petri Latvala
2019-06-19 11:51 ` [igt-dev] [PATCH i-g-t 6/6] runner/json_tests: Test dynamic subtests Petri Latvala
2019-06-19 15:03 ` [igt-dev] ✓ Fi.CI.BAT: success for Dynamic subtests Patchwork
2019-06-20  7:47 ` [igt-dev] [PATCH i-g-t 0/6] " Tvrtko Ursulin
2019-06-20  8:09   ` Petri Latvala
2019-06-21  9:26     ` Tvrtko Ursulin
2019-07-22 12:32       ` Petri Latvala
2019-08-02 14:23         ` Daniel Vetter [this message]
2019-06-20  9:06 ` [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=20190802142318.GO7444@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox