[Piglit] [REGRESSION] runtime of gpu.py doubled by commit 26326d4032631cdb4eb6816aada6c81db6f186d7
Michel Dänzer
michel at daenzer.net
Mon Apr 14 01:16:56 PDT 2014
On 12.04.2014 04:35, Dylan Baker wrote:
> On Tuesday, April 08, 2014 18:42:47 Michel Dänzer wrote:
>
> > I was away for the last two weeks, and when I came back I noticed that
> > gpu.py is now taking around 20 minutes to complete, whereas it only took
> > around 10 minutes before. I was able to bisect this to:
> >
> >
> > 26326d4032631cdb4eb6816aada6c81db6f186d7 is the first bad commit
> > commit 26326d4032631cdb4eb6816aada6c81db6f186d7
> > Author: Dylan Baker <baker.dylan.c at gmail.com>
> > Date: Wed Feb 5 15:44:37 2014 -0800
> >
> > framework/shader_test.py: simplify ShaderTest
> >
> >
> > This is on an A10-7850K (quad core Kaveri) APU FWIW.
>
> I believe that I have found the bug. See if the patch labeled: [PATCH]
> framework: Fix concurrency regression introduced by Test refactor
>
> fixes this problem for you.
Looks like that was it, thanks.
Any idea why you didn't notice the regression on your machine(s)?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
More information about the Piglit
mailing list