diff options
| author | Ruediger Meier | 2015-04-21 10:41:01 +0200 |
|---|---|---|
| committer | Ruediger Meier | 2015-04-21 14:58:30 +0200 |
| commit | fffe5f7c72121c054645c60c0bb49f653bb7142e (patch) | |
| tree | ffe8d9702ce1cc879d2a1d79ec08cc52e40d93f5 /tests/ts/fsck | |
| parent | tests: loop tests, don't call ts_die() with DEVICE parameter (diff) | |
| download | kernel-qcow2-util-linux-fffe5f7c72121c054645c60c0bb49f653bb7142e.tar.gz kernel-qcow2-util-linux-fffe5f7c72121c054645c60c0bb49f653bb7142e.tar.xz kernel-qcow2-util-linux-fffe5f7c72121c054645c60c0bb49f653bb7142e.zip | |
tests: never use -o pipefail
It was hard to find out that pipefail was the reason why our
test-suite could have random failures for aribtrary tests,
for example the ones which are using ts_device_has_uuid() or
ts_mount().
Bash's pipefall option is evil! It may return error for such a
simple line like this one
$ echo -e "xxx\nyyy" | grep -q "xxx"
because the left echo command will get SIGPIPE when grep exits after
the first match. So the command line above could return an error
eventhough it does exactly what we want.
This patch removes any pipefail from our tests. The funny thing is
that I couldn't find any case where we relied on this feature anyway.
Signed-off-by: Ruediger Meier <ruediger.meier@ga-group.nl>
Diffstat (limited to 'tests/ts/fsck')
| -rwxr-xr-x | tests/ts/fsck/ismounted | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/tests/ts/fsck/ismounted b/tests/ts/fsck/ismounted index 25bcff9e4..8edda4b6e 100755 --- a/tests/ts/fsck/ismounted +++ b/tests/ts/fsck/ismounted @@ -27,8 +27,6 @@ ts_check_prog "mkfs.ext3" ts_skip_nonroot ts_check_losetup -set -o pipefail - > $TS_OUTPUT ts_device_init |