2014-02-25 11:17:48 -05:00
|
|
|
#!/bin/bash
|
2014-04-08 00:14:19 -04:00
|
|
|
set -e
|
2014-02-25 11:17:48 -05:00
|
|
|
|
|
|
|
|
bundle_test_integration_cli() {
|
2016-03-11 14:06:56 -05:00
|
|
|
TESTFLAGS="$TESTFLAGS -check.v -check.timeout=${TIMEOUT} -timeout=360m"
|
2014-02-25 11:17:48 -05:00
|
|
|
go_test_dir ./integration-cli
|
|
|
|
|
}
|
|
|
|
|
|
2014-04-08 01:10:40 -04:00
|
|
|
# subshell so that we can export PATH without breaking other things
|
|
|
|
|
(
|
2015-04-20 06:21:21 -04:00
|
|
|
bundle .integration-daemon-start
|
2014-04-29 00:22:31 -04:00
|
|
|
|
2015-04-20 06:21:21 -04:00
|
|
|
bundle .integration-daemon-setup
|
2014-04-11 20:49:49 -04:00
|
|
|
|
Fix daemon start/stop logic in hack/make/* scripts
From the Bash manual's `set -e` description:
(https://www.gnu.org/software/bash/manual/bashref.html#index-set)
> Exit immediately if a pipeline (see Pipelines), which may consist of a
> single simple command (see Simple Commands), a list (see Lists), or a
> compound command (see Compound Commands) returns a non-zero status.
> The shell does not exit if the command that fails is part of the
> command list immediately following a while or until keyword, part of
> the test in an if statement, part of any command executed in a && or
> || list except the command following the final && or ||, any command
> in a pipeline but the last, or if the command’s return status is being
> inverted with !. If a compound command other than a subshell returns a
> non-zero status because a command failed while -e was being ignored,
> the shell does not exit.
Additionally, further down:
> If a compound command or shell function executes in a context where -e
> is being ignored, none of the commands executed within the compound
> command or function body will be affected by the -e setting, even if
> -e is set and a command returns a failure status. If a compound
> command or shell function sets -e while executing in a context where
> -e is ignored, that setting will not have any effect until the
> compound command or the command containing the function call
> completes.
Thus, the only way to have our `.integration-daemon-stop` script
actually run appropriately to clean up our daemon on test/script failure
is to use `trap ... EXIT`, which we traditionally avoid because it does
not have any stacking capabilities, but in this case is a reasonable
compromise because it's going to be the only script using it (for now,
at least; we can evaluate more complex solutions in the future if they
actually become necessary).
The alternatives were much less reasonable. One is to have the entire
complex chains in any script wanting to use `.integration-daemon-start`
/ `.integration-daemon-stop` be chained together with `&&` in an `if`
block, which is untenable. The other I could think of was taking the
body of these scripts out into separate scripts, essentially meaning
we'd need two files for each of these, which further complicates the
maintenance.
Add to that the fact that our `trap ... EXIT` is scoped to the enclosing
subshell (`( ... )`) and we're in even more reasonable territory with
this pattern.
Signed-off-by: Andrew "Tianon" Page <admwiggin@gmail.com>
2015-04-17 18:19:34 -04:00
|
|
|
bundle_test_integration_cli
|
2014-04-29 00:22:31 -04:00
|
|
|
|
2015-04-20 06:21:21 -04:00
|
|
|
bundle .integration-daemon-stop
|
2015-04-14 12:43:33 -04:00
|
|
|
) 2>&1 | tee -a "$DEST/test.log"
|