From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] scripts/run_tests.sh: Fix breakage after piglit updates.
Date: Tue, 19 Apr 2016 16:50:20 +0300 [thread overview]
Message-ID: <20160419135020.GU4329@intel.com> (raw)
In-Reply-To: <5716355E.8010501@linux.intel.com>
On Tue, Apr 19, 2016 at 03:40:46PM +0200, Maarten Lankhorst wrote:
> Op 19-04-16 om 15:38 schreef Ville Syrjälä:
> > On Tue, Apr 19, 2016 at 03:31:12PM +0200, Maarten Lankhorst wrote:
> >> Right now scripts/run-tests.sh fails with the following error message:
> >>
> >> Fatal Error: Cannot overwrite existing folder without the -o/--overwrite option being set.
> >>
> >> Fix this by adding -o as required.
> >>
> >> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >> ---
> >> diff --git a/scripts/run-tests.sh b/scripts/run-tests.sh
> >> index 99e6124f5279..f33b0ffd342a 100755
> >> --- a/scripts/run-tests.sh
> >> +++ b/scripts/run-tests.sh
> >> @@ -125,7 +125,7 @@ if [ "x$RESUME" != "x" ]; then
> >> sudo IGT_TEST_ROOT="$IGT_TEST_ROOT" "$PIGLIT" resume "$RESULTS" $NORETRY
> >> else
> >> mkdir -p "$RESULTS"
> > Just drop the mkdir instead?
> >
> In that case I wouldn't be able to retry in an existing directory.
Which some people may consider a good thing.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-19 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 13:31 [PATCH i-g-t] scripts/run_tests.sh: Fix breakage after piglit updates Maarten Lankhorst
2016-04-19 13:38 ` Ville Syrjälä
2016-04-19 13:40 ` Maarten Lankhorst
2016-04-19 13:50 ` Ville Syrjälä [this message]
2016-04-19 14:13 ` Marius Vlad
2016-04-19 14:23 ` Vivi, Rodrigo
2016-04-19 18:16 ` Dylan Baker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160419135020.GU4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.