On 2012/5/12 5:39, Kenneth Graunke wrote:
On 05/11/2012 02:04 AM, Shuang He wrote:
Before:
time ./piglit-print-commands.py -t 'asmparsertest/ARBfp1.0/size_specifier-31.txt' -x 'asmparsertest/ARBfp1.0/size_specifier-31.txt'.+ -x valgrind/ tests/all.tests asmparsertest/ARBfp1.0/size_specifier-31.txt ::: /GFX/Test/Piglit/piglit/framework/../bin/asmparsertest -auto ARBfp1.0 tests/asmparsertest/shaders/ARBfp1.0/size_specifier-31.txt

real    0m1.171s
user    0m1.132s
sys     0m0.039s

After:
time ./piglit-print-commands.py -t 'asmparsertest/ARBfp1.0/size_specifier-31.txt' -x 'asmparsertest/ARBfp1.0/size_specifier-31.txt'.+ -x valgrind/ tests/all.tests asmparsertest/ARBfp1.0/size_specifier-31.txt ::: /GFX/Test/Piglit/piglit/framework/../bin/asmparsertest -auto ARBfp1.0 tests/asmparsertest/shaders/ARBfp1.0/size_specifier-31.txt

real    0m0.331s
user    0m0.299s
sys     0m0.031s

Nice :)

For what it's worth, you don't need to pass -x valgrind anymore. I removed all the "valgrind tests" and just added a piglit-run.py --valgrind option.

Great, hopefully we could run piglit tests in our infrastructure very fast now :)

Thanks
    --Shuang
_______________________________________________
Piglit mailing list
Piglit@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/piglit

Reply via email to