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 v2] tests: Introduce i915 directory
Date: Fri, 19 Oct 2018 13:25:44 +0300	[thread overview]
Message-ID: <20181019102544.GQ17124@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <153994394922.19935.2916517710790645230@skylake-alporthouse-com>

On Fri, Oct 19, 2018 at 11:12:29AM +0100, Chris Wilson wrote:
> Quoting Petri Latvala (2018-10-19 11:02:18)
> > On Fri, Oct 19, 2018 at 11:48:54AM +0300, Arkadiusz Hiler wrote:
> > > We can already move all the tests with distinct prefixes: gem_, gen3_
> > > and i915_.
> > > 
> > > pm_ and drv_ tests will follow in batches, so we can do the
> > > adjustments in the reporting/filtering layer of the CI system.
> > > 
> > > v2: Fix test-list.txt generation with meson
> > > 
> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Petri Latvala <petri.latvala@intel.com>
> > > Cc: Martin Peres <martin.peres@linux.intel.com>
> > > Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> > 
> > Worth stating out loud why there's such a load of bovine excrement
> > needed for the autotools parts:
> > 
> > Test binaries all need to be in the same directory. After installing
> > it's easy to achieve but we also support running stuff from the build
> > directory directly. Ergo, we can't just make the tests/i915 directory
> > self-contained.
> 
> What are you talking about? Maybe explaining how amdgpu/ doesn't work,
> but we haven't given it any special treatment and you can run the
> compile binaries and it installs into the same targetdir as we haven't
> told it otherwise.

Yeah I wasn't quite clear on that one:

The test binary needs to be relative to the location of test-list.txt,
and for amdgpu the binary is amdgpu/amd_foobar. So to elaborate: The
reason is that we need to build the binaries into the tests directory
instead of tests/i915 or all tests will rename to i915/stuff@subtests
and 1) we avoid renaming tests when possible, to keep some resemblence
of test history and comparison capability 2) having / in the test name
is icky already with amdgpu. Quite soon we might be able to churn the
amdgpu tests to not have the /.


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

  reply	other threads:[~2018-10-19 10:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 12:58 [igt-dev] [PATCH i-g-t] tests: Introduce i915 directory Arkadiusz Hiler
2018-10-18 13:35 ` Lionel Landwerlin
2018-10-19  8:11   ` Arkadiusz Hiler
2018-10-19  8:33     ` Daniel Vetter
2018-10-18 13:44 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-10-18 20:24 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-10-18 21:21 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2018-10-19  8:48 ` [igt-dev] [PATCH i-g-t v2] " Arkadiusz Hiler
2018-10-19 10:02   ` Petri Latvala
2018-10-19 10:12     ` Chris Wilson
2018-10-19 10:25       ` Petri Latvala [this message]
2018-10-19 10:20 ` [igt-dev] [PATCH i-g-t v3] " Arkadiusz Hiler
2018-10-22 19:12 ` [igt-dev] ✓ Fi.CI.BAT: success for tests: Introduce i915 directory (rev3) Patchwork
2018-10-22 21:29 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20181019102544.GQ17124@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