[Piglit] piglit-run.py changed?

Jordan Justen jljusten at gmail.com
Wed May 7 11:15:36 PDT 2014

On Wed, May 7, 2014 at 8:27 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> On Wed, May 7, 2014 at 11:22 AM, Brian Paul <brianp at vmware.com> wrote:
>> I know there have been recent changes to the piglit python scripts but I
>> haven't been following them too closely.
>> It seems that piglit-run.py has changed in some way and I don't understand
>> what I'm supposed to do.
>> The following command is typical of what I'd run in the past, and it seems
>> to follow the the usage instructions, but it doesn't work:
>> $ ./piglit-run.py -t NV_conditional_render tests/all.py results
>> usage: piglit-run.py [-h] [-n <test name>] [-d] [-t <regex>] [-x <regex>]
>>                      [-c | -1] [-p {glx,x11_egl,wayland,gbm}] [-f
>>                      [--valgrind] [--dmesg] [-v]
>>                      <Path to one or more test profiles)>
>>                      [<Path to one or more test profile(s> ...] <Results
>> Path>
>> piglit-run.py: error: unrecognized arguments: results
>> Am I using piglit-run.py incorrectly?  Are the usage instructions out of
>> date?
> I'm guessing this is fallout from
> http://cgit.freedesktop.org/piglit/commit/?id=9b1e7da290cd612690e85bcacc99b50c65d83fe6
> ? Dylan? From what I could make out, any change to piglit-run.py
> command-line args would have been unintentional.

Yeah, I think this was unintentional.

Brian, you should also be able to replace ./piglit-run.py $* with
./piglit run $*.


More information about the Piglit mailing list