On Thu, Apr 5, 2018 at 2:05 PM, Dylan Baker <dy...@pnwbakers.com> wrote:
> Quoting Marek Olšák (2018-04-04 16:37:47) > > Is this use case affected? > > > > piglit run --deqp-mustpass-list --process-isolation 0 -p gbm -c quick > cts_gl45 > > deqp_gles2 deqp_gles3 deqp_gles31 > > You could either run that as: > > piglit run --deqp-mustpass-list --process-isolation 0 -p gbm -c quick_gl > quick_shader_multi glslparser cts_gl45 deqp_gles2 deqp_gles3 deqp_gles31 > > or you cold write yourself a metaprofile that would look something like: > > <?xml version="1.0" encoding="utf-8"?> > <PiglitMetaProfile> > <Profile>quick_gl</Profile> > <Profile>quick_shader_multi</Profile> > <Profile>glslparser</Profile> > <Profile>cts</Profile> > <Profile>gl45</Profile> > <Profile>deqp</Profile> > ... > </PiglitMetaProfile> > > We could probably put metaprofiles for the multiple-shader at a time > profiles > in piglit, I just didn't want to get too over board with them. > > > > > Yes, that is just 1 command to run all those test suites at the same > time. > > > > I use my personal "deqp" piglit branch that also disables process > isolation for > > glcts and deqp, and parses the deqp mustpass lists which are in txt > files. > > > > Marek > > I have not touched the --process-isolation flag since I knew that you had > that > branch (and I have a branch for dEQP as well that I might try to dust off > and > get working again). > Nicolai wrote the deqp and glcts patches removing process isolation. I've never looked at them and I probably wouldn't understand them either. Anybody is free to clean up them up and merge. Marek
_______________________________________________ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
