Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petri Latvala <petri.latvala@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt v2] igt/tools_test: Check the tools exist before executing
Date: Thu, 14 Dec 2017 14:39:35 +0200	[thread overview]
Message-ID: <a357b4ac-d5e5-00cf-8872-79886ecbe447@intel.com> (raw)
In-Reply-To: <151325066052.32659.4562567104853680541@mail.alporthouse.com>



On 12/14/2017 01:24 PM, Chris Wilson wrote:
> Quoting Petri Latvala (2017-12-14 11:20:18)
>> On Thu, Dec 14, 2017 at 11:14:35AM +0000, Chris Wilson wrote:
>>>> Why the chdir?
>>> For me, I was trying to standardise the test, since "../tools" bakes in
>>> so many assumptions that simply aren't true when one invokes
>>> $path/tools_test. Back to the igt_data_dir() request.
>> Aye, the assumption is bad and should get changed to support both run
>> methods (within build dir, with installed). Currently it works by
>> carefully setting up the CI deployment so paths match. =(
>>
>>>   
>>>> CI runs tests with IGT installed (make install). The test's directory
>>>> is $libexecdir/intel-gpu-tools/, ../tools is $libexecdir/tools and
>>>> that doesn't exist.
>>> So where was it expecting to find the tools?
>>
>> CI deploys the tools next to piglit. $cwd is piglit's directory when
>> running through piglit, tools are deployed to $piglit/../tools.
> How about
>
> if (access("../tools/", F_OK)) {
> 	chdir();
> }
>

Should be fine that way. Add a TODO comment somewhere about finding the 
directory for real.


-- 
Petri Latvala

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-12-14 12:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 17:22 [PATCH igt] igt/tools_test: Check the tools exist before executing Chris Wilson
2017-12-12 17:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-12 18:45 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-12-13  9:53 ` [PATCH igt] " Petri Latvala
2017-12-13 10:48 ` Joonas Lahtinen
2017-12-13 14:56 ` [PATCH igt v2] " Chris Wilson
2017-12-14 11:11   ` Petri Latvala
2017-12-14 11:14     ` Chris Wilson
2017-12-14 11:20       ` Petri Latvala
2017-12-14 11:24         ` Chris Wilson
2017-12-14 12:39           ` Petri Latvala [this message]
2017-12-13 17:16 ` ✓ Fi.CI.BAT: success for igt/tools_test: Check the tools exist before executing (rev2) Patchwork
2017-12-13 18:59 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-12-14 11:39 ` [PATCH igt v3] igt/tools_test: Check the tools exist before executing Chris Wilson
2017-12-14 11:57 ` ✗ Fi.CI.BAT: warning for igt/tools_test: Check the tools exist before executing (rev3) Patchwork
2017-12-14 21:57 ` ✓ Fi.CI.BAT: success " Patchwork
2017-12-14 23:38 ` ✗ Fi.CI.IGT: 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=a357b4ac-d5e5-00cf-8872-79886ecbe447@intel.com \
    --to=petri.latvala@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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