aboutgitcodebugslistschat
path: root/contrib/fedora/rpkg.macros
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2022-08-18 16:13:57 +1000
committerStefano Brivio <sbrivio@redhat.com>2022-08-20 19:07:12 +0200
commit3fdb0747f36d63d6f1a2724181a56e10f7065f4b (patch)
tree4987326c27101c087d4817925744317820c936da /contrib/fedora/rpkg.macros
parent69126d4d48002784562ba44a77df37387968061d (diff)
downloadpasst-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar.gz
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar.bz2
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar.lz
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar.xz
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.tar.zst
passt-3fdb0747f36d63d6f1a2724181a56e10f7065f4b.zip
test: Log debugging output from test script
The test scripts run with sh -e, which means they will stop if any commands return an error. That's generally desirable, because we won't continue after things are hopeless due to an earlier step failing. Unfortunately, the tmux setup we run the script in means it's not obvious where any error messages related to such a failure will go. Depending on exactly where the error occurs they might go to the original terminal hidden behind tmux, or they might go to a tmux panel that's not visible in the normal layouts. To make it easier to find such error message, redirect direct output and errors from the test script itself to a 'script.log' file in the logs directory. When in DEBUG=1 mode, additionaly 'set -x' so we log all the commands we execute to that file. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'contrib/fedora/rpkg.macros')
0 files changed, 0 insertions, 0 deletions