On Tue, Aug 04, 2015 at 02:54:56PM -0700, Dylan Baker wrote:
> > On Tue, Aug 4, 2015 at 2:39 AM, Daniel Vetter wrote:
> >
> > Doesn't this have the effect of accidentally removing old results you
> > might want to keep if you do a type (with e.g. shell completion)? Old
> > piglit refused to run if
On Tue, Aug 4, 2015 at 2:39 AM, Daniel Vetter wrote:
>
> Doesn't this have the effect of accidentally removing old results you
> might want to keep if you do a type (with e.g. shell completion)? Old
> piglit refused to run if the results dir was there iirc, so maybe we need
> a --force-overwrite o
On Mon, Aug 03, 2015 at 04:46:22PM -0700, Dylan Baker wrote:
> This prevents piglit from aggregating tests from a previous run into the
> new run by deleting the old tests directory before starting.
>
> Signed-off-by: Dylan Baker
> ---
> framework/programs/run.py | 10 +-
> 1 file change
This prevents piglit from aggregating tests from a previous run into the
new run by deleting the old tests directory before starting.
Signed-off-by: Dylan Baker
---
framework/programs/run.py | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/framework/programs/run.py b
