mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
bdcd81d330
Looks like -i (together with DOCKER_INCREMENTAL_BINARY etc) were used to get faster incremental builds. Nowdays (since Go 1.10) this is no longer the case, as go build cache is used [1]. Here's a quote: > You do not have to use "go test -i" or "go build -i" or > "go install" just to get fast incremental builds. We will > not have to teach new users those workarounds anymore. > Everything will just be fast. To enable go cache between builds, add a volume for /root/.cache. [1] https://groups.google.com/forum/#!msg/golang-dev/qfa3mHN4ZPA/X2UzjNV1BAAJ Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
34 lines
780 B
Bash
Executable file
34 lines
780 B
Bash
Executable file
#!/usr/bin/env bash
|
|
#
|
|
# Run unit tests
|
|
#
|
|
# TESTFLAGS - add additional test flags. Ex:
|
|
#
|
|
# TESTFLAGS="-v -run TestBuild" hack/test/unit
|
|
#
|
|
# TESTDIRS - run tests for specified packages. Ex:
|
|
#
|
|
# TESTDIRS="./pkg/term" hack/test/unit
|
|
#
|
|
set -eu -o pipefail
|
|
|
|
TESTFLAGS+=" -test.timeout=${TIMEOUT:-5m}"
|
|
BUILDFLAGS=( -tags "netgo seccomp libdm_no_deferred_remove" )
|
|
TESTDIRS="${TESTDIRS:-"./..."}"
|
|
|
|
exclude_paths="/vendor/|/integration"
|
|
pkg_list=$(go list $TESTDIRS | grep -vE "($exclude_paths)")
|
|
|
|
for pkg in $pkg_list; do
|
|
go test "${BUILDFLAGS[@]}" \
|
|
-cover \
|
|
-coverprofile=profile.out \
|
|
-covermode=atomic \
|
|
$TESTFLAGS \
|
|
"${pkg}"
|
|
|
|
if test -f profile.out; then
|
|
cat profile.out >> coverage.txt
|
|
rm profile.out
|
|
fi
|
|
done
|