csonto
/
bash-completion
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Run delegated test tools/scripts with exec.

master
Ville Skyttä 2010-04-21 23:34:27 +03:00
parent f9f49786ca
commit c5348d8678
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/run
View File

@ -57,4 +57,4 @@ done
[[ -n $timeout ]] && args+=("OPT_TIMEOUT=$timeout")
[[ -z $tool ]] && { echo "Must specify tool somehow"; exit 1; }
runtest --outdir log --tool $tool "${args[@]}"
exec runtest --outdir log --tool $tool "${args[@]}"

2
test/runCompletion
View File

@ -4,4 +4,4 @@
# isn't initialized at that point (i.e. output of `expect' is shown on
# stdout - `open_logs' hasn't run yet?). And running code from a library
# file isn't probably a good idea either.
"$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool completion $*
exec "$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool completion $*

2
test/runInstall
View File

@ -4,4 +4,4 @@
# isn't initialized at that point (i.e. output of `expect' is shown on
# stdout - `open_logs' hasn't run yet?). And running code from a library
# file isn't probably a good idea either.
runtest --outdir log --tool install $*
exec runtest --outdir log --tool install $*

2
test/runUnit
View File

@ -4,4 +4,4 @@
# isn't initialized at that point (i.e. output of `expect' is shown on
# stdout - `open_logs' hasn't run yet?). And running code from a library
# file isn't probably a good idea either.
"$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool unit $*
exec "$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool unit $*