]> git.ipfire.org Git - thirdparty/bind9.git/commit
Store system test output in bin/tests/system/
authorMichał Kępień <michal@isc.org>
Fri, 6 Dec 2019 13:11:01 +0000 (14:11 +0100)
committerMichał Kępień <michal@isc.org>
Fri, 6 Dec 2019 13:47:08 +0000 (14:47 +0100)
commit38a4bedfcd84b7f2704fd8dbc034f5339700fcbd
tree9e601dbb7494cc57e42cddaf8c4fd909a19e4df9
parent8ed6c8fd5919bab0080ef949fbbbd2bd7e213048
Store system test output in bin/tests/system/

Some clean.sh scripts contain overly broad file deletion wildcards which
cause the test.output file (used by the system test framework for
collecting output) in a given system test's directory to be erroneously
removed immediately after the test is started (due to setup.sh scripts
calling clean.sh at the beginning).  This prevents the test's output
from being placed in bin/tests/system/systests.output at the end of a
test suite run and thus can lead to test failures being ignored.  Fix by
storing each test's output in a test.output.<test-name> file in
bin/tests/system/, which prevents clean.sh scripts from removing it (as
they should only ever affect files contained in a given system test's
directory).

(cherry picked from commit b0916bba41b2898185c91a9ddc07dea42d1bdfaa)
bin/tests/system/.gitignore
bin/tests/system/README
bin/tests/system/cleanall.sh
bin/tests/system/parallel.sh
bin/tests/system/runsequential.sh
bin/tests/system/testsummary.sh