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 26326d4032631cdb4eb6816a
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:
>
>
> 26326d4032631cdb4eb6816aada6c8
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:
>
>
> 26326d4032631cdb4eb6816aada6c8
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:
>
>
> 26326d4032631cdb4eb6816aada6c8
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
On Monday, April 14, 2014 05:16:56 PM Michel Dänzer wrote:
> 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,
