aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNicolas George <nicolas.george@normalesup.org>2013-01-02 23:22:46 +0100
committerNicolas George <nicolas.george@normalesup.org>2013-01-03 16:16:07 +0100
commitbe01d1a24ddca88bded154f5fae77c6373e67cfe (patch)
tree470dd514841fe3cc979a5620a8cdd1cd03188c65
parent1894302a44f3babe736fabd78e168a70cb16ffac (diff)
downloadffmpeg-be01d1a24ddca88bded154f5fae77c6373e67cfe.tar.gz
fate: disable globbing when calling shell functions.
Some of the filters tests use globbing characters, especially brackets for filter pad labels. While most of these strings are way too complicated to ever match an existing file name and are therefore kept unchanged in the command line (an old misfeature of the shell language that happens to be convenient here), at least one use is simple enough to match random files lying in the current directory. If that happens, the string, that was meant to be kept verbatim, is replaced by the file name, and that causes the test to fail (or worse).
-rwxr-xr-xtests/fate-run.sh4
1 files changed, 4 insertions, 0 deletions
diff --git a/tests/fate-run.sh b/tests/fate-run.sh
index 9cd872b6c6..0520d62f7d 100755
--- a/tests/fate-run.sh
+++ b/tests/fate-run.sh
@@ -166,6 +166,10 @@ lavfitest(){
mkdir -p "$outdir"
+# Disable globbing: command arguments may contain globbing characters and
+# must be kept verbatim
+set -f
+
exec 3>&2
eval $command >"$outfile" 2>$errfile
err=$?