Re: [Piglit] Deleting ~20% of glean/no more directory spam

2013-01-03 Thread Eric Anholt
Kenneth Graunke kenn...@whitecape.org writes: This series deletes roughly 20% of Piglit's import of Glean: I'm pretty sure I reviewed your series back when you pointed me at the branch, so I'm happy to see it land. pgpch7NBgO1UV.pgp Description: PGP signature

Re: [Piglit] Deleting ~20% of glean/no more directory spam

2013-01-02 Thread Paul Berry
On 31 December 2012 18:40, Kenneth Graunke kenn...@whitecape.org wrote: Now that Piglit's import of Glean is beginning to diverge from Glean proper, my hope is that someday people will port over various tests to the native Piglit framework, then delete the equivalent Glean code. A bit more

Re: [Piglit] Deleting ~20% of glean/no more directory spam

2013-01-01 Thread Brian Paul
On Mon, Dec 31, 2012 at 7:40 PM, Kenneth Graunke kenn...@whitecape.org wrote: Now that Piglit's import of Glean is beginning to diverge from Glean proper, my hope is that someday people will port over various tests to the native Piglit framework, then delete the equivalent Glean code. A bit

Re: [Piglit] Deleting ~20% of glean/no more directory spam

2013-01-01 Thread Marek Olšák
These tests aren't sufficiently covered by piglit tests and should be kept: - fragProg1 (our main test for ARB_fragment_program, the piglit tests aren't so useful as this one) - paths (the only test for polygon stippling apart from pbo?) - pbo - stencil2 (tests glStencilMaskSeparate) - vertProg1

[Piglit] Deleting ~20% of glean/no more directory spam

2012-12-31 Thread Kenneth Graunke
This series deletes roughly 20% of Piglit's import of Glean: 1. Benchmarking Piglit is a not a benchmarking suite---it's a test suite. It has no infrastructure for even running these tests, so there's no need to keep them around. 2. Image output code Jose nuked most of this,