b42c5e5fad
To make sure we build the exact version of btcd that is referenced in the project's go.mod file and to not overwrite any binary the user might already have installed on the system, we compile btcd into an explicit file in the itest directory. This should also speed up invocations of "make itest-only" because the test harness doesn't always compile btcd on its own. We also fix a bug with the version parsing where adding a "replace" directive in the go.mod would result in the awk commands to extract the wrong version. Because we no longer use the DEPGET goal to build and install btcd, using a replace directive now actually works for itests.
25 lines
975 B
Bash
Executable File
25 lines
975 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# Let's work with absolute paths only, we run in the itest directory itself.
|
|
WORKDIR=$(pwd)/lntest/itest
|
|
|
|
TRANCHE=$1
|
|
NUM_TRANCHES=$2
|
|
|
|
# Shift the passed parameters by two, giving us all remaining testing flags in
|
|
# the $@ special variable.
|
|
shift
|
|
shift
|
|
|
|
# Windows insists on having the .exe suffix for an executable, we need to add
|
|
# that here if necessary.
|
|
EXEC="$WORKDIR"/itest.test"$EXEC_SUFFIX"
|
|
LND_EXEC="$WORKDIR"/lnd-itest"$EXEC_SUFFIX"
|
|
BTCD_EXEC="$WORKDIR"/btcd-itest"$EXEC_SUFFIX"
|
|
echo $EXEC -test.v "$@" -logoutput -goroutinedump -logdir=.logs-tranche$TRANCHE -lndexec=$LND_EXEC -btcdexec=$BTCD_EXEC -splittranches=$NUM_TRANCHES -runtranche=$TRANCHE
|
|
|
|
# Exit code 255 causes the parallel jobs to abort, so if one part fails the
|
|
# other is aborted too.
|
|
cd "$WORKDIR" || exit 255
|
|
$EXEC -test.v "$@" -logoutput -goroutinedump -logdir=.logs-tranche$TRANCHE -lndexec=$LND_EXEC -btcdexec=$BTCD_EXEC -splittranches=$NUM_TRANCHES -runtranche=$TRANCHE || exit 255
|