On Tue, Sep 13, 2016 at 11:12 PM, Dylan Baker wrote:
> Quoting Dylan Baker (2016-09-13 13:46:11)
>> Quoting Marek Olšák (2016-09-13 13:27:21)
>> > On Tue, Sep 13, 2016 at 8:30 PM, Dylan Baker wrote:
>> > > So, there were a few comments I've addressed,
Quoting Dylan Baker (2016-09-13 13:46:11)
> Quoting Marek Olšák (2016-09-13 13:27:21)
> > On Tue, Sep 13, 2016 at 8:30 PM, Dylan Baker wrote:
> > > So, there were a few comments I've addressed, and Marek acked one patch.
> > > Do y'all want to see a v2, or should I just push
Quoting Marek Olšák (2016-09-13 13:27:21)
> On Tue, Sep 13, 2016 at 8:30 PM, Dylan Baker wrote:
> > So, there were a few comments I've addressed, and Marek acked one patch.
> > Do y'all want to see a v2, or should I just push this?
>
> There are at least 2 piglit regressions
On Tue, Sep 13, 2016 at 8:30 PM, Dylan Baker wrote:
> So, there were a few comments I've addressed, and Marek acked one patch.
> Do y'all want to see a v2, or should I just push this?
There are at least 2 piglit regressions with --process-isolation 0:
On Sat, Sep 10, 2016, at 06:56, Marek Olšák wrote:
> Thanks a lot of doing this!!
>
> BTW, --no-process-isolation is not a valid parameter.
Yeah, I decided to change the parameter after I ran the benchmarks, when
I was writing documentation and proper commit messages. I realized that
I'd
Thanks for doing that, the numbers are impressive.
Two small comments on the C parts; it's been too long since I looked
into the Python parts to be able to properly comment.
Cheers,
Nicolai
On 09.09.2016 21:18, Dylan Baker wrote:
This allows shader_runner to consume more than one test at a
This allows shader_runner to consume more than one test at a time. When
it does this it reports the results as subtests rather than as regular
tests. It also updates the python framework to handle and resume from
crashes in the tests. When this mode is enabled, shader_runner runs an
entire