bind9/bin/tests/system/runsequential.sh
Michał Kępień b0916bba41 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).
2019-12-06 14:11:01 +01:00

25 lines
767 B
Bash
Executable file

#!/bin/sh
#
# Copyright (C) Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
#
# See the COPYRIGHT file distributed with this work for additional
# information regarding copyright ownership.
# Run system tests that must be run sequentially
#
# Note: Use "make check" (or runall.sh) to run all the system tests. This
# script will just run those tests that require that each of their nameservers
# is the only one running on an IP address.
#
SYSTEMTESTTOP=.
. $SYSTEMTESTTOP/conf.sh
for d in $SEQUENTIALDIRS
do
$SHELL run.sh "${@}" $d 2>&1 | tee test.output.$d
done