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,
	Martin Peres <martin.peres@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/1] runner: Add explicit "notrun" results for tests that were not executed
Date: Wed, 14 Nov 2018 13:33:07 +0200	[thread overview]
Message-ID: <20181114113307.GX17124@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <154211582600.16646.8154900673673094531@skylake-alporthouse-com>

On Tue, Nov 13, 2018 at 01:30:26PM +0000, Chris Wilson wrote:
> Quoting Petri Latvala (2018-11-13 13:04:30)
> > When possible, all tests we know we were going to attempt to execute
> > now appear in the results as "notrun". The only known case where it's
> > not possible to add an explicit "notrun" is when running in
> > multiple-mode, because "no subtests" and "run all subtests, we didn't
> > list them beforehand" are represented the same.
> 
> Sounds strange for a runner with which we can integrate with the igt
> framework not know whether or not a test started. Although the easiest
> procedure would seem to be that all tests should include at least one
> igt_subtest().

That wouldn't work for the case I'm describing. Although it seems I
didn't describe it in enough detail. And there's a different case
lurking there too.

When running in multiple-mode, if you specified e.g. -t kms_flip, the
job list creation sees that the binary "kms_flip" is enough to match
that filter, ergo, we run all subtests of that binary, we don't need
to execute kms_flip --list-subtests to get the subtest list
explicitly. The job list will contain:

 kms_flip

If we also specified e.g. -t testdisplay, the job list will contain:

 kms_flip
 testdisplay

Now, the purpose of this patch was for Martin to know from the results
what our pass rate is, and for that he needs the list of all tests,
and we can get there by explicitly getting a "notrun" for tests that
didn't get executed (due to an incomplete). We can't know what
kms_flip subtests to get the result for, because we didn't list
them. Knowing that it _has_ subtests doesn't help.

For Intel CI, this is a moot point because we use testlists
everywhere. Even with multiple-mode, we get the full list of subtests
explicitly stated and we can fill in "notrun" for them.


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

  reply	other threads:[~2018-11-14 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 13:04 [igt-dev] [PATCH i-g-t 1/1] runner: Add explicit "notrun" results for tests that were not executed Petri Latvala
2018-11-13 13:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/1] " Patchwork
2018-11-13 13:30 ` [igt-dev] [PATCH i-g-t 1/1] " Chris Wilson
2018-11-14 11:33   ` Petri Latvala [this message]
2018-11-13 13:52 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2018-11-13 15:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-12-05 14:51 ` [igt-dev] [PATCH i-g-t 1/1] " Martin Peres

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=20181114113307.GX17124@platvala-desk.ger.corp.intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@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