On 05/07/2014 12:15 PM, Jordan Justen wrote:
On Wed, May 7, 2014 at 8:27 AM, Ilia Mirkin <[email protected]> wrote:
On Wed, May 7, 2014 at 11:22 AM, Brian Paul <[email protected]> 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
CONFIG_FILE]
[--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
https://urldefense.proofpoint.com/v1/url?u=http://cgit.freedesktop.org/piglit/commit/?id%3D9b1e7da290cd612690e85bcacc99b50c65d83fe6&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=lGQMzzTgII0I7jefp2FHq7WtZ%2BTLs8wadB%2BiIj9xpBY%3D%0A&m=l0ucY4hgl6C5aRAvZOmHAC3vSAPYodF6SSWHOpfIH10%3D%0A&s=fa2b35bb4e1be61340c980168766b4739ac17831891d27b59c2c0dd84271766d
? 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 $*.
Yeah, that works. Thanks!
-Brian
_______________________________________________
Piglit mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/piglit
