[Piglit] [PATCH] piglit-run.py: record whether the test run was concurrent

Dylan Baker baker.dylan.c at gmail.com
Thu Nov 14 15:05:56 PST 2013


On Thursday, November 14, 2013 09:47:57 PM Damien Lespiau wrote:
> On Thu, Nov 14, 2013 at 01:16:02PM -0800, Ben Widawsky wrote:
> > On Thu, Nov 14, 2013 at 08:52:19PM +0000, Damien Lespiau wrote:
> > > On Thu, Nov 14, 2013 at 10:44:37AM -0800, Dylan Baker wrote:
> > > > cc: ben at bwidawsk.net
> > > > Signed-off-by: Dylan Baker <baker.dylan.c at gmail.com>
> > > 
> > > Can you also make sure the concurrency option is correctly loaded from
> > > the json file in the resume path?
> > > 
> > > Thanks,
> > 
> > Does resume enforce it is run with the same options as before?
> 
> It does for the filters (-x, -t), and it'd be handy to do it for the
> concurrency option in my opinion.

Yes, if resume allows you to change setting's it is inherently broken becasue 
it is unrepeatable. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20131114/1f970cb9/attachment-0001.pgp>


More information about the Piglit mailing list