]> git.ipfire.org Git - thirdparty/bind9.git/commit
Call clean.sh from all relevant setup.sh scripts
authorMichał Kępień <michal@isc.org>
Thu, 28 Feb 2019 11:33:07 +0000 (12:33 +0100)
committerMichał Kępień <michal@isc.org>
Thu, 28 Feb 2019 11:39:06 +0000 (12:39 +0100)
commit7b1f4c8a6a1e505896aa6ca8de3a0b876a8d3f09
treedadbcc63038159857775da33edc4b42729d99a95
parentc2c957735f8f6964d5e5a2774602a6d38c32cb81
Call clean.sh from all relevant setup.sh scripts

For all system tests utilizing named instances, call clean.sh from each
test's setup.sh script in a consistent way to make sure running the same
system test multiple times using run.sh does not trigger false positives
caused by stale files created by previous runs.

Ideally we would just call clean.sh from run.sh, but that would break
some quirky system tests like "rpz" or "rpzrecurse" and being consistent
for the time being does not hurt.

(cherry picked from commit a077a3ae8a5013e089bb4e6f9ab8137c5b708dce)
17 files changed:
bin/tests/system/autosign/setup.sh
bin/tests/system/case/setup.sh
bin/tests/system/dlv/setup.sh
bin/tests/system/dlzexternal/setup.sh
bin/tests/system/dsdigest/setup.sh
bin/tests/system/dupsigs/setup.sh
bin/tests/system/ecdsa/setup.sh
bin/tests/system/eddsa/setup.sh
bin/tests/system/ixfr/setup.sh
bin/tests/system/masterformat/setup.sh
bin/tests/system/metadata/setup.sh
bin/tests/system/pending/setup.sh
bin/tests/system/pkcs11/setup.sh
bin/tests/system/resolver/setup.sh
bin/tests/system/serve-stale/setup.sh
bin/tests/system/staticstub/setup.sh
bin/tests/system/stress/setup.sh