public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, Tomi Sarvela <tomi.p.sarvela@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib: Update selftests to use dynamic subtests
Date: Mon, 17 Feb 2020 13:01:30 +0200	[thread overview]
Message-ID: <20200217110130.GH25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20200214214829.4054673-1-chris@chris-wilson.co.uk>

On Fri, Feb 14, 2020 at 09:48:29PM +0000, Chris Wilson wrote:
> Use the new igt_subtest_with_dynamic to nicely group the dynamic
> subtests together.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>
> ---
>  lib/igt_kmod.c | 23 +++++++++++++++++++----
>  1 file changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
> index 05019c24c..e701545d3 100644
> --- a/lib/igt_kmod.c
> +++ b/lib/igt_kmod.c
> @@ -21,6 +21,7 @@
>   * IN THE SOFTWARE.
>   */
>  
> +#include <ctype.h>
>  #include <signal.h>
>  #include <errno.h>
>  
> @@ -602,6 +603,18 @@ void igt_kselftest_fini(struct igt_kselftest *tst)
>  	kmod_module_unref(tst->kmod);
>  }
>  
> +static const char *unfilter(const char *filter, const char *name)
> +{
> +	if (!filter)
> +		return name;
> +
> +	name += strlen(filter);
> +	if (!isalpha(*name))
> +		name++;
> +
> +	return name;
> +}
> +
>  void igt_kselftests(const char *module_name,
>  		    const char *options,
>  		    const char *result,
> @@ -618,10 +631,12 @@ void igt_kselftests(const char *module_name,
>  		igt_require(igt_kselftest_begin(&tst) == 0);
>  
>  	igt_kselftest_get_tests(tst.kmod, filter, &tests);
> -	igt_list_for_each_entry_safe(tl, tn, &tests, link) {
> -		igt_subtest_f("%s", tl->name)
> -			igt_kselftest_execute(&tst, tl, options, result);
> -		free(tl);
> +	igt_subtest_with_dynamic(filter ?: "all") {
> +		igt_list_for_each_entry_safe(tl, tn, &tests, link) {
> +			igt_dynamic_f("%s", unfilter(filter, tl->name))
> +				igt_kselftest_execute(&tst, tl, options, result);
> +			free(tl);
> +		}
>  	}



Thanks for starting this, exactly what dynamic subtests are for.

Pre-acked-by: Petri Latvala <petri.latvala@intel.com>

CI side should be made ready before landing this. With kernel
selftests being now launched from statically enumerable subtests,
selftests can be added to fast-feedback.testlist and un-blacklisted
from shards where applicable.

Tomi, what do we run (and what do we want to) in BAT now? Objections
to running selftests in shards mixed in with other tests?

Runtime is a concern if all (FSVO all) selftests are launched with one
entry in a testlist. What is the total runtime on a random platform
for, say, i915_selftest subtests (post patch)? We might need to split
more than just live/mock.


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

  parent reply	other threads:[~2020-02-17 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 21:48 [igt-dev] [PATCH i-g-t] lib: Update selftests to use dynamic subtests Chris Wilson
2020-02-14 22:53 ` [igt-dev] ✗ GitLab.Pipeline: failure for " Patchwork
2020-02-14 23:05 ` [igt-dev] ✗ Fi.CI.BAT: " Patchwork
2020-02-17 11:01 ` Petri Latvala [this message]
2020-02-17 11:17   ` [igt-dev] [PATCH i-g-t] " Petri Latvala
2020-02-17 11:22     ` Chris Wilson
2020-02-17 11:26       ` Petri Latvala
2020-02-17 11:32         ` Chris Wilson
2020-02-17 12:38           ` Petri Latvala
2020-02-17 11:36   ` Sarvela, Tomi P
2020-02-17 12:44 ` [igt-dev] [PATCH i-g-t v2] " Chris Wilson
2020-02-17 13:16 ` [igt-dev] ✗ GitLab.Pipeline: warning for lib: Update selftests to use dynamic subtests (rev3) Patchwork
2020-02-17 15:59 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=20200217110130.GH25209@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tomi.p.sarvela@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