All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Wood <thomas.wood@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [i-g-t 1/7] README: update piglit instructions
Date: Tue, 10 Jun 2014 16:06:17 +0100	[thread overview]
Message-ID: <CANkqdn1DXQnTbjUXg7Rz9-X_VBXwuFgCC-_0djkBfq+ZjzVsDA@mail.gmail.com> (raw)
In-Reply-To: <20140610143714.GT5821@phenom.ffwll.local>

On 10 June 2014 15:37, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Tue, Jun 10, 2014 at 03:30:51PM +0100, Thomas Wood wrote:
>> Piglit now has a top level "piglit" command and the location of the
>> tests can now be read from an environment variable.
>>
>> Signed-off-by: Thomas Wood <thomas.wood@intel.com>
>> ---
>>  README | 27 ++++++++++-----------------
>>  1 file changed, 10 insertions(+), 17 deletions(-)
>>
>> diff --git a/README b/README
>> index 2cfb5c5..cfa186d 100644
>> --- a/README
>> +++ b/README
>> @@ -34,32 +34,25 @@ tests/
>>
>>       git://anongit.freedesktop.org/piglit
>>
>> -     and build it (no need to install anything). Then we need to link up the
>> -     i-g-t sources with piglit
>> +     There is no need to build and install piglit if it is only going to be
>> +     used for running i-g-t tests.
>> +
>> +     Set the IGT_TEST_ROOT environment variable to point to the tests
>> +     directory or link up the i-g-t sources with piglit using a symlink:
>>
>>       piglit-sources $ cd bin
>>       piglit-sources/bin $ ln $i-g-t-sources igt -s
>>
>> -     To avoid some hassles with piglit's use of Waffle just disable it. Run
>> -
>> -     piglit-sources $ cmake -D PIGLIT_USE_WAFFLE=OFF .
>> -
>> -     With
>> -
>> -     piglit-sources $ ccmake .
>> -
>> -     you can check your configuration with a curses interface, too.
>
> Hm, why did you drop this? I run into "lack of waffle" every time I try to
> use piglit ... Otherwise looks good.

Since there's no need to actually build the Piglit test cases when
running intel-gpu-tools tests, there's no requirement for waffle
either.


> -Daniel
>
>> -
>> -     The tests in the i-g-t sources need to have been built already. Then we
>> -     can run the testcases with (as usual as root, no other drm clients
>> -     running):
>> +     In both cases, the tests in the i-g-t sources need to have been built
>> +     already. Then we can run the testcases with (as usual as root, no other
>> +     drm clients running):
>>
>> -     piglit-sources # ./piglit-run.py igt <results-file>
>> +     piglit-sources # ./piglit run igt <results-file>
>>
>>       The testlist is built at runtime, so no need to update anything in
>>       piglit when adding new tests. See
>>
>> -     piglit-sources $ ./piglit-run.py -h
>> +     piglit-sources $ ./piglit run -h
>>
>>       for some useful options.
>>
>> --
>> 1.9.3
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-06-10 15:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 14:30 [i-g-t 1/7] README: update piglit instructions Thomas Wood
2014-06-10 14:30 ` [i-g-t 2/7] lib: remove /** from comments that are not API documentation Thomas Wood
2014-06-10 14:30 ` [i-g-t 3/7] README: update the section on modifying and rebuilding documentation Thomas Wood
2014-06-10 14:38   ` Daniel Vetter
2014-06-11 10:33     ` Thomas Wood
2014-06-10 14:30 ` [i-g-t 4/7] docs: add the sections file Thomas Wood
2014-06-10 14:40   ` Daniel Vetter
2014-06-11 10:35     ` Thomas Wood
2014-06-11 11:56       ` Daniel Vetter
2014-06-11 14:49         ` [PATCH i-g-t] docs: always rebuild " Thomas Wood
2014-06-10 14:30 ` [i-g-t 5/7] gitignore: add missing files and keep lists sorted Thomas Wood
2014-06-10 14:30 ` [i-g-t 6/7] lib: various documentation fixes Thomas Wood
2014-06-10 14:44   ` Daniel Vetter
2014-06-10 14:30 ` [i-g-t 7/7] docs: add missing sections to intel-gpu-tools-docs.xml Thomas Wood
2014-06-10 14:47   ` Daniel Vetter
2014-06-11 10:36     ` Thomas Wood
2014-06-11 10:53       ` [PATCH i-g-t] docs: add private headers to IGNORE_HFILES Thomas Wood
2014-06-11 11:57         ` Daniel Vetter
2014-06-10 14:37 ` [i-g-t 1/7] README: update piglit instructions Daniel Vetter
2014-06-10 15:06   ` Thomas Wood [this message]
2014-06-10 15:28     ` Daniel Vetter

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=CANkqdn1DXQnTbjUXg7Rz9-X_VBXwuFgCC-_0djkBfq+ZjzVsDA@mail.gmail.com \
    --to=thomas.wood@intel.com \
    --cc=daniel@ffwll.ch \
    --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 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.