Skip to content

Commit

Permalink
tests: don't write files when running functional test compile check
Browse files Browse the repository at this point in the history
We recently added a script to compile the functional test go code as
a faster (and more frequently run) sanity check. However, the
go command line tool defaults to writing a <pkg>.test binary when
asked to compile test code. We tell the go tool to write the result
to /dev/null so we don't generate unwanted artifacts any more.

Signed-off-by: John Mulligan <jmulligan@redhat.com>
  • Loading branch information
phlogistonjohn authored and obnoxxx committed Mar 26, 2018
1 parent 0091f7e commit 5a7d4dc
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion tests/100-compile-functest-go.sh
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ TAGS="functional dbexamples"
find tests/functional -name '*.go' -print0 | \
xargs -0 dirname | sort -u | \
sed -e 's,^/*,github.com/heketi/heketi/,' | \
xargs -L1 go test -c -tags "$TAGS"
xargs -L1 go test -c -o /dev/null -tags "$TAGS"

0 comments on commit 5a7d4dc

Please sign in to comment.