On Fri, Nov 20, 2015 at 11:19 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote: > Right... so I'm looking for concrete things I can look for in tests to > determine whether the run_concurrent=False is set incorrectly. I know > the *approximate* reasons, but I'd like to be certain and then go grep > it all and remove the run_concurrent flag from 75% of those that have > it (either by updating the test or by determining that it has no need > to be run single threaded).
Incorrect or not, any person valuing his own time uses the "-c" flag, which makes all tests concurrent. I haven't seen any randomness in piglit results from that besides one or two timing tests which I happily ignore. Marek _______________________________________________ Piglit mailing list Piglit@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/piglit
