Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-21 Thread Marek Olšák
I actually agree with the patch. I was just making a suggestion. It seems nobody has NAK'd this patch yet. :) Marek On Thu, Aug 21, 2014 at 11:24 AM, Michel Dänzer wrote: > On 21.08.2014 17:57, Marek Olšák wrote: >> >> I recommend using the -c option. It will force concurrency for all >> tests.

Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-21 Thread Michel Dänzer
On 21.08.2014 17:57, Marek Olšák wrote: > > I recommend using the -c option. It will force concurrency for all > tests. With that, I don't care which tests aren't concurrent by > default. That might break the non-concurrent tests without a compositing manager, which I don't want to use for piglit

Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-21 Thread Marek Olšák
Hi Michel, I recommend using the -c option. It will force concurrency for all tests. With that, I don't care which tests aren't concurrent by default. Marek On Wed, Aug 20, 2014 at 5:13 AM, Michel Dänzer wrote: > From: Michel Dänzer > > This reverts commit acb824ddc53c446124d88e37db610a4f8c59d

Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-20 Thread Dylan Baker
On Wednesday, August 20, 2014 12:13:11 PM Michel Dänzer wrote: > From: Michel Dänzer > > This reverts commit acb824ddc53c446124d88e37db610a4f8c59d56c. > > This decreases the runtime of the gpu.py profile from around 15 minutes to > around 12 minutes on my machine, with no change in results. > >

Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-20 Thread Michel Dänzer
On 21.08.2014 05:42, Jason Ekstrand wrote: > On Aug 19, 2014 8:13 PM, "Michel Dänzer" > wrote: >> >> From: Michel Dänzer > >> >> This reverts commit acb824ddc53c446124d88e37db610a4f8c59d56c. >> >> This decreases the runtime of the gpu.py p

Re: [Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-20 Thread Jason Ekstrand
On Aug 19, 2014 8:13 PM, "Michel Dänzer" wrote: > > From: Michel Dänzer > > This reverts commit acb824ddc53c446124d88e37db610a4f8c59d56c. > > This decreases the runtime of the gpu.py profile from around 15 minutes to > around 12 minutes on my machine, with no change in results. Do you use a comp

[Piglit] [PATCH] Allow one 'non-concurrent' test to run in parallel with concurrent tests again

2014-08-19 Thread Michel Dänzer
From: Michel Dänzer This reverts commit acb824ddc53c446124d88e37db610a4f8c59d56c. This decreases the runtime of the gpu.py profile from around 15 minutes to around 12 minutes on my machine, with no change in results. If in the future there are tests which really can't run in parallel with any o