On Monday, November 17, 2014 11:30:13 AM Mark Janes wrote: > spec.EXT_timer_query.time-elapsed fails intermittently, causing > confusion for developers running quick.py to find regressions. This > test has always been intermittent, and people generally know to ignore > it when it fails. > > However, if everyone ignores the test, there is no point in running it > all the time. > --- > tests/quick.py | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/tests/quick.py b/tests/quick.py > index 8762d7d..802501c 100644 > --- a/tests/quick.py > +++ b/tests/quick.py > @@ -12,3 +12,4 @@ del profile.tests['shaders']['glsl-fs-inline-explosion'] > del profile.tests['shaders']['glsl-fs-unroll-explosion'] > del profile.tests['shaders']['glsl-vs-inline-explosion'] > del profile.tests['shaders']['glsl-vs-unroll-explosion'] > +del profile.tests['spec']['EXT_timer_query']['time-elapsed'] > -- > 2.1.3 >
I think I've seen all of the EXT_timer_query and all of the ARB_timer_query fail sporadicly. Should we just disable all of those groups?
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
