aboutgitcodebugslistschat
path: root/test/demo/pasta
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2022-05-12 12:42:50 +1000
committerStefano Brivio <sbrivio@redhat.com>2022-05-19 15:24:15 +0200
commit3e0641f91f7296dca67224babc221f3a161224e1 (patch)
treef4337a32150a9c0e8219c55601e2bb3a61ebe80d /test/demo/pasta
parentc638129a9e803388a37d95c4c411047571556109 (diff)
downloadpasst-3e0641f91f7296dca67224babc221f3a161224e1.tar
passt-3e0641f91f7296dca67224babc221f3a161224e1.tar.gz
passt-3e0641f91f7296dca67224babc221f3a161224e1.tar.bz2
passt-3e0641f91f7296dca67224babc221f3a161224e1.tar.lz
passt-3e0641f91f7296dca67224babc221f3a161224e1.tar.xz
passt-3e0641f91f7296dca67224babc221f3a161224e1.tar.zst
passt-3e0641f91f7296dca67224babc221f3a161224e1.zip
tests: Don't ignore errors during script
Most commands issued during the testing scripts aren't explicitly checked for errors. Therefore, if they fail, the shell will just keep on executing. This makes it difficult to figure out where things started going wrong if things fall over. Run the whole script with the set -e mode so that it will exit in the case of any (unchecked) failing command. To make this work we do need to add explicit checks / fallbacks for some commands which we expect to fail. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> [sbrivio: use sh -e instead of setting -e later, so that we don't miss anything before set -e is issued] Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test/demo/pasta')
0 files changed, 0 insertions, 0 deletions