[Piglit] [PATCH] framework: Don't stop resume because no tests are left to be run
dylan at pnwbakers.com
Thu Jul 20 16:21:10 UTC 2017
Quoting Matt Turner (2017-07-19 18:17:22)
> On Tue, Jul 11, 2017 at 10:27 AM, Dylan Baker <dylan at pnwbakers.com> wrote:
> > It's completely possible that if piglit resume is run with the -n flag
> > (don't retry incomplete tests), that piglit resume could be invoked with
> > no tests left to run. In this case it makes sense to let piglit resume
> > just finalize the backend and produce a unified result.
> > Signed-off-by: Dylan Baker <dylanx.c.baker at intel.com>
> > cc: Martin Peres <martin.peres at linux.intel.com>
> > ---
> > framework/programs/run.py | 15 ++++++++++-----
> > 1 file changed, 10 insertions(+), 5 deletions(-)
> > diff --git a/framework/programs/run.py b/framework/programs/run.py
> > index 508bc05c4..ef268f722 100644
> > --- a/framework/programs/run.py
> > +++ b/framework/programs/run.py
> > @@ -35,6 +35,7 @@ import six
> > from framework import core, backends, exceptions, options
> > from framework import dmesg
> > +from framework import exceptions
> exceptions looks like it's imported a few lines above. Is this intentional?
No, I apparently just can't read.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
More information about the Piglit