This is a bug that has existed for a long time, and I'm not really sure
how we haven't hit this before honestly, I think that the reason this
has worked is that we've always provided a concrete type to to
pool.imap.
The problem is that pool.imap is an iterator. If you don't walk the
results then t
Michel, does this series fix the remaining issues you're seeing?
Dylan
Quoting Dylan Baker (2018-05-08 14:22:04)
> This is a bug that has existed for a long time, and I'm not really sure
> how we haven't hit this before honestly, I think that the reason this
> has worked is that we've always prov
On 2018-05-08 11:27 PM, Dylan Baker wrote:
> Michel, does this series fix the remaining issues you're seeing?
It mostly fixes the gpu profile running fewer tests than before. The
only remaining minor issue there is that the
shaders@glsl-{fs,vs}-{inline,unroll}-explosion tests were previously
accur
Quoting Michel Dänzer (2018-05-09 02:33:13)
> On 2018-05-08 11:27 PM, Dylan Baker wrote:
> > Michel, does this series fix the remaining issues you're seeing?
>
> It mostly fixes the gpu profile running fewer tests than before. The
> only remaining minor issue there is that the
> shaders@glsl-{fs,v
Quoting Michel Dänzer (2018-05-09 02:33:13)
> On 2018-05-08 11:27 PM, Dylan Baker wrote:
> > Michel, does this series fix the remaining issues you're seeing?
>
> It mostly fixes the gpu profile running fewer tests than before. The
> only remaining minor issue there is that the
> shaders@glsl-{fs,v
On 2018-05-09 07:38 PM, Dylan Baker wrote:
> Quoting Michel Dänzer (2018-05-09 02:33:13)
>> On 2018-05-08 11:27 PM, Dylan Baker wrote:
>>
>> The bigger remaining issue is that --process-isolation false gpu takes
>> almost twice as long as it did before
>> 9461d92301e72807eba4776a16a05207e3a16477.
>
