On 05.06.2014 16:48, Dylan Baker wrote: > On Thursday, June 05, 2014 12:50:26 PM Michel Dänzer wrote: >> On 25.04.2014 07:51, Marek Olšák wrote: >>> There are 3 categories of tests: >>> - concurrent, these are off-screen and can be run anytime >>> - non-concurrent, because they render to a window (usually a front >>> buffer) and may take focus; any number of off-screen tests can be run >>> simultaneously with these, because off-screen tests cannot affect >>> front buffer rendering in other apps >>> - non-concurrent, because they measure time and therefore should be >>> run while all the other processes are idle (we really have like 2 or 3 >>> of these) >> >> I fully agree with Marek on this. It would be great if somebody could >> work on distinguishing between the second and third case above, and >> allowing one second case test to run concurrently with first case tests >> again. This would cut down the runtime of gpu.py by several minutes for me. > > If you have a compositor you could always just use the -c option and run all > of the tests concurrently.
BTW, if that was really a workable solution, there was no need for the change that spawned this thread in the first place. :) -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Piglit mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/piglit
