[Piglit] Ideas for Wine Test Suite and Mesa Workflow

2016-02-16 Thread Zhenbo Li
Hello, I'm Zhenbo Li, applying for Wine's GSoC 2016[1]. I hope this project can accelerate further development for both Wine and Mesa. My idea has been discussed in wine-devel[2], but I'm sure whether it helps Mesa. While reading documents for Piglit, I got this idea: Write a scrip

Re: [Piglit] Ideas for Wine Test Suite and Mesa Workflow

2016-02-21 Thread Zhenbo Li
;m going to send it to this mail list few days later. Thank you. [1]: For example, run `wine d3d10_crosstest.exe --list`, one can get Valid test names: device effect And here are 10 subtests in effect: constant_buffer_stride constant_buffer_type get_variable_by local_shader

Re: [Piglit] Ideas for Wine Test Suite and Mesa Workflow

2016-02-24 Thread Zhenbo Li
2016-02-21 21:38 GMT+08:00 Zhenbo Li : > > I think I can write a functional python script, and submit it to wine. > In mesa, it needs to do > little(more simple than piglit/tests/igt.py). I'm writing a proof of > concept test(piglit/tests/wine) > now, and I'm going to s

Re: [Piglit] Ideas for Wine Test Suite and Mesa Workflow

2016-02-27 Thread Zhenbo Li
t real0m12.117s user0m0.705s sys 0m0.345s If I use a python wrapper[1], I got $ rm -rf ~/.wine && make clean && make $ cd dlls/msxml3/tests $ time python3 runner.py real0m12.633s user0m0.702s sys 0m0.368s [1]: runner.py #!/usr/bin/env python3 import os ret

Re: [Piglit] Ideas for Wine Test Suite and Mesa Workflow

2016-02-27 Thread Zhenbo Li
2016-02-27 22:38 GMT+08:00 Zhenbo Li : > > Thank you for pointing it out. I think it is not so critical. > I ran such code (in path/to/wine/code) Sorry, I made a mistake. I need to catch the output, so subprocess is necessary. $ time python runner.py real0m12.158s user0m2