https://bugs.freedesktop.org/show_bug.cgi?id=104214
--- Comment #54 from Jason Ekstrand <ja...@jlekstrand.net> ---
(In reply to Thomas Hellström from comment #53)
> So IMHO we should try to write piglit tests for the areas where we know
> there are remaining issues.
That's a reasonable thing to say. However, our DRI testing in piglit is rather
pitiful across the board IMHO. Part of the reason why you had to fix 6
different bugs in order to turn on DRI3 is that we've been lazy about testing
when working on the DRI code. Window system stuff is annoyingly full of
edge-cases and the piglit tests we have tend to only touch-test things. This
is only one of the 3 or 4 DRI bugs we've shipped in the last few months that
piglit has been perfectly happy with and then it messes up users badly.
While I would love to give someone the general task of improving piglit testing
of DRI, a good place to start is to write tests for known bugs. If we have a
really nasty threading bug, let's make a test that hammers on threading.
Ok, I've said my piece. Maybe I'm being unreasonable but it sounds good in my
head. :-)
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
