All the Glean tests that check for specific rendering results already
have an error margin.
Can you be more specific about which tests are failing and how the error
margin might need to be changed?
-Brian
Oliver McFadden wrote:
I notice some failures with the example tests (R300) that seem
On 3/18/07, Brian Paul [EMAIL PROTECTED] wrote:
All the Glean tests that check for specific rendering results already
have an error margin.
Can you be more specific about which tests are failing and how the error
margin might need to be changed?
-Brian
I previously replied (but forgot to
Nicolai Haehnle wrote:
Hello,
back when I was actively working on DRI drivers almost three years
ago, I always felt uneasy about the fact that I didn't have an
extensive array of tests that I could rely on to test for regressions.
Now I've decided to do something about it. I've taken
I notice some failures with the example tests (R300) that seem to just be
slight precision errors; I think you should add a margin for error because
usually the hardware will implement things in a faster, perhaps less precise
way.
This lower precision is still good enough, though.
On 3/17/07,
