From: Daniel Vetter <daniel@ffwll.ch>
To: "Gore, Tim" <tim.gore@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 2/2] intel-gpu-tools: Re-use igt_subtest_init for simple tests
Date: Wed, 9 Jul 2014 16:23:50 +0200 [thread overview]
Message-ID: <20140709142350.GX17271@phenom.ffwll.local> (raw)
In-Reply-To: <8FCC70911F3E9548866CA0E51893BCC31A1CDD53@IRSMSX105.ger.corp.intel.com>
On Wed, Jul 09, 2014 at 01:23:46PM +0000, Gore, Tim wrote:
> Some comments on Daniels' comments inline
>
> > -----Original Message-----
> > From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel
> > Not sure whether forcing the reuse of igt_subtest_init makes a lot of sense
> > since it requires a lot of follow-up changes all over. I'd just add a bit of
> > argparsing here with the required special cases, i.e.
> > - exit without doing anything for --list-subtests
> > - exit with 77 when anything is specified with --run-subtests
> >
> What I wanted to do here was start removing the distinction between single
> Tests and multiple test; this distinction seems somewhat artificial and doesn't
> seem to add much.
> igt_subtest_init does pretty much everything we want for single tests
> so I thought it made sense to re-use it. Perhaps the name should change,
> although this would lead to more knock on changes.
Well under the hood subtests work with longjmps when skipping/failing
tests while simple tests directly call exit. The reason for that is that
historically we've started with simple binaries and slowly grew the igt
infrastructure on top of them. I don't really see much benefits in
converting the last stragglers.
> > Also I prefer if the piglit changes come together with this patch so that we
> > can roll it all out together.
>
> What piglet changes do you refer to? I have not made any piglit changes.
For me the only trouble with this disdinction is that people consistently
place tests in the wrong Makefile target. Hence I'd like to see those two
Makefile targets being unified (which requires adjustements in piglit,
too) to validate this work. Iirc Thomas is also working on this.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-09 14:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 14:15 [PATCH 0/2] Single tests to respond to --list-subtests tim.gore
2014-06-27 14:15 ` [PATCH 1/2] intel-gpu-tools: pass argc/argv to simple main tim.gore
2014-07-01 9:19 ` Thomas Wood
2014-07-07 16:12 ` Daniel Vetter
2014-07-09 13:50 ` Gore, Tim
2014-07-09 14:20 ` Daniel Vetter
2014-06-27 14:15 ` [PATCH 2/2] intel-gpu-tools: Re-use igt_subtest_init for simple tests tim.gore
2014-07-01 9:26 ` Thomas Wood
2014-07-07 16:09 ` Daniel Vetter
2014-07-09 13:23 ` Gore, Tim
2014-07-09 14:23 ` Daniel Vetter [this message]
2014-07-09 16:42 ` Damien Lespiau
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=20140709142350.GX17271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tim.gore@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