From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC i-g-t v2] igt: Test tagging support
Date: Sat, 22 Jul 2017 16:43:09 +0300 [thread overview]
Message-ID: <87d18smvte.fsf@intel.com> (raw)
In-Reply-To: <20170721102005.3073-1-tvrtko.ursulin@linux.intel.com>
On Fri, 21 Jul 2017, Tvrtko Ursulin <tursulin@ursulin.net> wrote:
> Proposal to add test tags as a replacement for separate test
> list which can be difficult to maintain and get out of date.
>
> Putting this maintanenace inline with tests makes it easier
> to remember to update the (now implicit) lists, and also enables
> richer test selection possibilities for the test runner.
>
> Current method of implying tags from test/subtest names has a
> couple of problems one of which is where some names can use
> the same token for different meanings. (One example is the
> "default" token.) It also creates a name clash between naming
> and tagging.
I'll say this once more, and then I'll shut up.
I think it's fundamentally the wrong thing to do to put the tags in the
test sources themselves. It should be enough to look at the commit churn
we had to move tests to/from BAT before we had test lists to be
convinced. You shouldn't have to modify the tests to tag/untag them.
You'll also find it'll be an interesting and needed feature to be able
to have tags that aren't committed to the public repo. This would fail
completely if you needed to have commits touching all the tests you need
to tag. And we don't want to maintain both the test list and the tagging
thing.
This is the "I told you so" mail I'll reference in the future.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-07-22 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 10:20 [RFC i-g-t v2] igt: Test tagging support Tvrtko Ursulin
2017-07-21 10:36 ` Chris Wilson
2017-07-21 11:08 ` Tvrtko Ursulin
2017-07-21 11:27 ` Chris Wilson
2017-07-21 11:54 ` Tvrtko Ursulin
2017-07-21 12:02 ` Martin Peres
2017-07-21 12:17 ` Tvrtko Ursulin
2017-07-21 12:22 ` Martin Peres
2017-07-21 12:59 ` Chris Wilson
2017-07-21 15:59 ` Daniel Vetter
2017-07-21 15:55 ` Daniel Vetter
2017-07-22 13:43 ` Jani Nikula [this message]
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=87d18smvte.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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.