On 03/16/2015 06:37 PM, Matt Turner wrote:
On Mon, Mar 16, 2015 at 4:54 AM, Tapani Pälli <tapani.pa...@intel.com> wrote:
Is there some particular Piglit test case that hits this path and is it
possible with gen>5 (by removing gen check)? I've tried this with
handicrafted shader_test and also shader-db and cannot hit the conditions
for changes to happen. Would be nice to be able to run examine changes and
understand this better.
Well, from the shader-db stats there must be some shaders affected in shader-db.
Use INTEL_DEVID_OVERRIDE=... with a Gen4 or Gen5 PCI ID from
include/pci_ids/i965_pci_ids.h.
Yeah, got that but run.py for me says following error so I did not want
to try manually go one by one. The amount of tests it runs before error
changes between runs.
--- 8< ---
[tpalli@localhost shader-db]$ ./run.py shaders
shaders/humus-domino/1.shader_test vs : 14 0.073 secs
shaders/nexuiz/43.shader_test vs : 25 0.092 secs
shaders/anholt/12.shader_test vs : 8 0.062 secs
Traceback (most recent call last):
File "./run.py", line 149, in <module>
main()
File "./run.py", line 142, in main
for t in executor.map(run_test, filenames):
File "/usr/lib64/python3.4/concurrent/futures/_base.py", line 549, in
result_iterator
yield future.result()
File "/usr/lib64/python3.4/concurrent/futures/_base.py", line 395, in
result
return self.__get_result()
File "/usr/lib64/python3.4/concurrent/futures/_base.py", line 354, in
__get_result
raise self._exception
File "/usr/lib64/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "./run.py", line 95, in run_test
counts[current_type] = counts[current_type] + 1
KeyError: 'UNKNOWN'
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
