ec94874c1e
This is first commit from the series introducing funcrional tests for setup.sh. Issues like #1689, #1691 showed that major changes to setup.sh may result in quite unexpected behavior. thus to avoid any regression, we should make sure the core of its functionality is properly tested. For now, only Linux systems are supported tests-wise. The tests are explicitly run after all OCSSD are put into PCI_BLOCKED to make sure they won't be picked up by the tests. Change-Id: Iac036e693bdbaac476faea3d2128cf4d95434cb2 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5308 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
10 lines
188 B
Bash
10 lines
188 B
Bash
source "$rootdir/test/common/autotest_common.sh"
|
|
|
|
setup() {
|
|
if [[ $1 == output ]]; then
|
|
"$rootdir/scripts/setup.sh" "${@:2}"
|
|
else
|
|
"$rootdir/scripts/setup.sh" "$@" &> /dev/null
|
|
fi
|
|
}
|