d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
3d4b9ba0d4
numam-spdk/autotest.sh

365 lines
11 KiB
Bash
Raw Normal View History

build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
#!/usr/bin/env bash
rootdir=$(readlink -f $(dirname $0))
test/common: Disable autotest options by default. By default most of the tests are enabled, if we want to run only tests that interests us, we need to disable each flag separatly. Build SPDK without additional dependencies and exit autotest.sh early if no test configuration file is provided. Change-Id: Id4752689479d9325242364c39c89d1236bab0344 Signed-off-by: Pawel Niedzwiecki <pawelx.niedzwiecki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/443762 Reviewed-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-07 12:22:12 +00:00
# In autotest_common.sh all tests are disabled by default.
# If the configuration of tests is not provided, no tests will be carried out.
autotest: don't source the configuration file in every test script Most of our bash test scripts source autotest_common.sh to be able to use some autotest-specific functions like timing_enter(). The same test scripts allow specifying custom command line parameters without actually realizing that those parameters can be potentially picked up by autotest_common.sh as well. For example, if particular nvmf tests are run in "isolation" mode by being executed with the first param set to "iso", and there is a file named "iso" in the current dir, that file will be sourced. This could be bad. In this patch we stop sourcing or even processing $1 in autotest_common.sh. Instead, the test configuration will be sourced just once from autobuild.sh, autopackage.sh and autotest.sh. If the user wants to run particular test scripts manually, he should source an SPDK test configuration by himself - manually as well. In most cases he won't even have two, as only a few test scripts depend on SPDK_* variables. Note that we still have to setup the default values for SPDK_* variables in autotest_common.sh because some of our test scripts actually depend on them: > if [ $SPDK_TEST_RBD -eq 1 ]; then ... Because it lacks any type of quotes around SPDK_TEST_RBD, it will print the following message when that variable is unset: > /bin/bash: line 0: [: -eq: unary operator expected It doesn't trigger any error ($? == 0), but can be still a bit misleading in the script output. Change-Id: I350045d8582d66fe1ed7697d4bcbba324cb541ad Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/453876 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-05-09 11:22:41 +00:00
if [[ ! -f $1 ]]; then
echo "ERROR: SPDK test configuration not specified"
test/common: Disable autotest options by default. By default most of the tests are enabled, if we want to run only tests that interests us, we need to disable each flag separatly. Build SPDK without additional dependencies and exit autotest.sh early if no test configuration file is provided. Change-Id: Id4752689479d9325242364c39c89d1236bab0344 Signed-off-by: Pawel Niedzwiecki <pawelx.niedzwiecki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/443762 Reviewed-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-07 12:22:12 +00:00
exit 1
fi
autobuild: add SPDK_TEST_NATIVE_DPDK to test again pristine DPDK master This was previously done in a Jenkins script. Move it to autobuild.sh inside the repo where we can all see it. Use new meson/ninja build system while at it. To test, use autorun.sh with the following cfg options: SPDK_RUN_EXTERNAL_DPDK=/tmp/spdk/dpdk/build SPDK_TEST_NATIVE_DPDK=1 SPDK_RUN_EXTERNAL_DPDK can point to a different path, but needs to have correct access permissions for current user, I had to reorder some code in autobuild.sh. Since SPDK_RUN_EXTERNAL_DPDK needs to specified the ./configure script can't be run without existing dpdk directory, so the dpdk build needs to happen before the initial ./configure as well as the ocf pre-build. Change-Id: Ibc57094806b361dc3c6acf55942f04a938e5194f Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/868 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-02-13 08:30:50 +00:00
# always test with SPDK shared objects.
export SPDK_LIB_DIR="$rootdir/build/lib"
autobuild.sh: fix ipsec installation for custom dpdk - Enable shared objects - Lininkg to libs for meson done with -Dc_link_args - append lib path to LD_LIBRARY_PATH in case ipsec is needed in later build or test steps - Save LD_LIBRARY_PATH from autobuild.sh and pass it to autotest.sh. This is needed for crypto tests using ipsec-intel-mb library. Change-Id: I047c6d3187ea42de8790181428d18596b195ff2e Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4730 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Michal Berger <michalx.berger@intel.com>
2020-10-16 06:51:32 +00:00
# Autotest.sh, as part of autorun.sh, runs in a different
# shell process than autobuild.sh. Use helper file to pass
# over env variable containing libraries paths.
if [[ -e /tmp/spdk-ld-path ]]; then
source /tmp/spdk-ld-path
fi
autotest: don't source the configuration file in every test script Most of our bash test scripts source autotest_common.sh to be able to use some autotest-specific functions like timing_enter(). The same test scripts allow specifying custom command line parameters without actually realizing that those parameters can be potentially picked up by autotest_common.sh as well. For example, if particular nvmf tests are run in "isolation" mode by being executed with the first param set to "iso", and there is a file named "iso" in the current dir, that file will be sourced. This could be bad. In this patch we stop sourcing or even processing $1 in autotest_common.sh. Instead, the test configuration will be sourced just once from autobuild.sh, autopackage.sh and autotest.sh. If the user wants to run particular test scripts manually, he should source an SPDK test configuration by himself - manually as well. In most cases he won't even have two, as only a few test scripts depend on SPDK_* variables. Note that we still have to setup the default values for SPDK_* variables in autotest_common.sh because some of our test scripts actually depend on them: > if [ $SPDK_TEST_RBD -eq 1 ]; then ... Because it lacks any type of quotes around SPDK_TEST_RBD, it will print the following message when that variable is unset: > /bin/bash: line 0: [: -eq: unary operator expected It doesn't trigger any error ($? == 0), but can be still a bit misleading in the script output. Change-Id: I350045d8582d66fe1ed7697d4bcbba324cb541ad Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/453876 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-05-09 11:22:41 +00:00
source "$1"
autotest_common.sh: move to test/common This is the first step in reorganizing the spdk test heirarchy. Change-Id: I83467653af2da2a53251649092bed6902d6cb86e Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/401707 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-02-27 22:14:08 +00:00
source "$rootdir/test/common/autotest_common.sh"
test/nvmf: only run RDMA NIC setup once Change-Id: I69607670de95652f997712ad3e7441718c97e3ab Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-08 21:19:11 +00:00
source "$rootdir/test/nvmf/common.sh"
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
if [ $EUID -ne 0 ]; then
echo "$0 must be run as root"
exit 1
fi
autotest: set core_pattern to a known value Change-Id: Ib0aaa441c17fb5c042dde751ec244c9e9f38a0c7 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-06 16:26:13 +00:00
if [ $(uname -s) = Linux ]; then
test/common: Always attempt to restore core_pattern This setting may be crucial on some systems in keeping core dump files in order, that's why we should always make sure it's main value is restored upon exiting from autotest.sh. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I0c81a8c96c2d8f061e95c2614d9c30f4e3cdd5a6 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3605 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-07-30 14:15:19 +00:00
old_core_pattern=$(< /proc/sys/kernel/core_pattern)
scripts: Use core dump collector This is done in order to track core dumps in a more efficient manner. Till now, some cores could be missed if the binary was executed outside of the cwd of the autotest (i.e. outside of the spdk repo) but which was part of the critical path of the actual test (e.g. fio in vhost-initiator tests). Also, since core_pattern was set to plain "core", impact on the underlying storage wasn't controlled either - if core was 20G in size, this is what we would get. This could easly exhaust storage in case error-prone patchsets were submitted on the CI side. The collector will try to mitigate all the above by doing the following: - collecting all the cores, regardless of their cwd - limiting size of the core to 2G - compressing the cores (lz4) Also, limit of 2 collectors executing at once is set - if more processes crashes at approx. the same time, they will be logged in the kernel log instead. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I5956a9030c463ae85a21bfe95f28af5568c5c285 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5369 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-12-01 11:57:47 +00:00
mkdir -p "$output_dir/coredumps"
autotest: set core_pattern to a known value Change-Id: Ib0aaa441c17fb5c042dde751ec244c9e9f38a0c7 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-06 16:26:13 +00:00
# set core_pattern to a known value to avoid ABRT, systemd-coredump, etc.
scripts: Use core dump collector This is done in order to track core dumps in a more efficient manner. Till now, some cores could be missed if the binary was executed outside of the cwd of the autotest (i.e. outside of the spdk repo) but which was part of the critical path of the actual test (e.g. fio in vhost-initiator tests). Also, since core_pattern was set to plain "core", impact on the underlying storage wasn't controlled either - if core was 20G in size, this is what we would get. This could easly exhaust storage in case error-prone patchsets were submitted on the CI side. The collector will try to mitigate all the above by doing the following: - collecting all the cores, regardless of their cwd - limiting size of the core to 2G - compressing the cores (lz4) Also, limit of 2 collectors executing at once is set - if more processes crashes at approx. the same time, they will be logged in the kernel log instead. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I5956a9030c463ae85a21bfe95f28af5568c5c285 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5369 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-12-01 11:57:47 +00:00
echo "|$rootdir/scripts/core-collector.sh %P %s %t $output_dir/coredumps" > /proc/sys/kernel/core_pattern
echo 2 > /proc/sys/kernel/core_pipe_limit
test: modprobe nbd at the start of autotest This helps avoid issues with nbd not being ready when we need it. Still keep various "modprobe nbd" in different test files - this ensures these test files can still be run in isolation. But remove the various "rmmod nbd" to ensure that nbd always stays loaded. There is no harm in just keeping nbd loaded all the time. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I3597ff1f7ac53162c33a0384a33f33776cf6f182 Reviewed-on: https://review.gerrithub.io/434838 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-11-26 08:04:25 +00:00
autotest: clear system caches before running setup.sh. This will help avoid the recent error with not being able to allocate enough hugepages on VMs. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: Iaf495458210da79501c7168104efe97c63b7afc7 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2212 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2020-05-06 20:34:57 +00:00
# Make sure that the hugepage state for our VM is fresh so we don't fail
test/autotest: sleep after clearing hugepage cache Give the system some time to clear the hugepage cache after we kick off that operation. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: I18de5feee500dae456c6ba3d9759085bc6f4e96e Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2280 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-05-08 15:49:49 +00:00
# hugepage allocation. Allow time for this action to complete.
autotest: clear system caches before running setup.sh. This will help avoid the recent error with not being able to allocate enough hugepages on VMs. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: Iaf495458210da79501c7168104efe97c63b7afc7 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2212 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2020-05-06 20:34:57 +00:00
echo 1 > /proc/sys/vm/drop_caches
test/autotest: sleep after clearing hugepage cache Give the system some time to clear the hugepage cache after we kick off that operation. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: I18de5feee500dae456c6ba3d9759085bc6f4e96e Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2280 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-05-08 15:49:49 +00:00
sleep 3
autotest: clear system caches before running setup.sh. This will help avoid the recent error with not being able to allocate enough hugepages on VMs. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: Iaf495458210da79501c7168104efe97c63b7afc7 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2212 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2020-05-06 20:34:57 +00:00
test: modprobe nbd at the start of autotest This helps avoid issues with nbd not being ready when we need it. Still keep various "modprobe nbd" in different test files - this ensures these test files can still be run in isolation. But remove the various "rmmod nbd" to ensure that nbd always stays loaded. There is no harm in just keeping nbd loaded all the time. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I3597ff1f7ac53162c33a0384a33f33776cf6f182 Reviewed-on: https://review.gerrithub.io/434838 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2018-11-26 08:04:25 +00:00
# make sure nbd (network block device) driver is loaded if it is available
# this ensures that when tests need to use nbd, it will be fully initialized
modprobe nbd || true
test/common: Log all system uevents during autotest This may be useful in debugging and pinpointing devices which may take longer time to initialize during the tests. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I5abad17e1a2690a063b6152462dcf49d22c70d0f Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3656 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-08-03 14:01:53 +00:00
if udevadm=$(type -P udevadm); then
"$udevadm" monitor --property &> "$output_dir/udev.log" &
udevadm_pid=$!
fi
autotest: set core_pattern to a known value Change-Id: Ib0aaa441c17fb5c042dde751ec244c9e9f38a0c7 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-06 16:26:13 +00:00
fi
autotest: Make sure entire EXIT trap is executed process_core() indicates error where any core files are found. If that happens to be the case when the trap is called, the remaining pieces won't be executed due to errexit being enabled. With that in mind, simply ignore process_core's exit status. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I83527468bd1b41bf92b9ee8189a4c425be914552 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6990 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-03-22 10:59:30 +00:00
trap "process_core || :; autotest_cleanup; exit 1" SIGINT SIGTERM EXIT
autotest: capture core dumps on early exits Change-Id: Ic1bb518ecd8d5fba42c7f0b86cbf02524c262f0e Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-25 16:48:11 +00:00
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
timing_enter autotest
autotest: add test completion tracking Change-Id: I1ca0578a010db2ff8535505bfd981cd1c368e403 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/392240 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2017-12-18 21:20:41 +00:00
create_test_list
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
src=$(readlink -f $(dirname $0))
autotest.sh: save lcov files in output_dir Coverage and ut_coverage files would get created in spdk dir or in directory from which the autotest.sh was called. Use $output_dir provided by autotest_common.sh instead to keep all build artifacts in common place. Signed-off-by: Karol Latecki <karol.latecki@intel.com> Change-Id: Iaf009182441933cb5e9bd137d0c94078272dd749 Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1134 Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-03-04 15:54:51 +00:00
out=$output_dir
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
cd $src
autobuild: On FreeBSD, install the contigmem driver The contigmem driver is built with dpdk and frequently updated. We should copy this driver each time we build dpdk in order to maintain support for FreeBSD kldload checks the sysctl variable kern.module_path when deciding which modules to load. Since the values stored in this variable are not determined by our program, I chose to copy the module to both common directories for kernel modules in FreeBSD. Change-Id: I2d439a9cbac5bebb79e6ee48bec47409bb215be9 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/409250 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-04-26 23:46:08 +00:00
freebsd_update_contigmem_mod
autotest: Fix for disable lcov when using clang Previous commit #ddba844, has wrong path in unittest.sh and missing checks in unittest.sh and autotest.sh, that here was fixed. Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Idc12719c0d427e3e6ec1a0e2c57e899508b0d7f5 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5364 Reviewed-by: Karol Latecki <karol.latecki@intel.com> 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> Community-CI: Mellanox Build Bot
2020-12-01 07:48:29 +00:00
# lcov takes considerable time to process clang coverage.
# Disabling lcov allow us to do this.
# More information: https://github.com/spdk/spdk/issues/1693
CC_TYPE=$(grep CC_TYPE mk/cc.mk)
if hash lcov && ! [[ "$CC_TYPE" == *"clang"* ]]; then
unittests: add local UT coverage Collect coverage info when running UT locally when lcov is available. Change-Id: I34a8b60056775a25cd4a3906d59c4a42e7cc845f Signed-off-by: paul luse <paul.e.luse@intel.com>
2017-05-08 20:57:23 +00:00
# setup output dir for unittest.sh
export UT_COVERAGE=$out/ut_coverage
lcov: enable branch coverage Change-Id: Idf98cf36c2e1080d204a475272302e0d7229a280 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-11-11 20:09:51 +00:00
export LCOV_OPTS="
--rc lcov_branch_coverage=1
--rc lcov_function_coverage=1
--rc genhtml_branch_coverage=1
--rc genhtml_function_coverage=1
--rc genhtml_legend=1
--rc geninfo_all_blocks=1
"
lcov: ignore external files in coverage data Rather than removing external coverage data at the end, just don't capture it at all. Change-Id: I23b74a4aa735e470b642af76040d1c3ed491276f Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-09-13 17:16:41 +00:00
export LCOV="lcov $LCOV_OPTS --no-external"
build: print lcov version to log Signed-off-by: Jim Harris <james.r.harris@intel.com> Requested-by: Lance Hartmann Change-Id: Ied379648754a7f61d902c9454539f63117122e1f Reviewed-on: https://review.gerrithub.io/399433 Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2018-02-12 15:59:50 +00:00
# Print lcov version to log
$LCOV -v
build: add CONFIG_COVERAGE code coverage option Collect coverage information for use with gcov. Coverage is disabled on FreeBSD because the current version of clang provided by FreeBSD can't successfully link with -ftest-coverage enabled (the compiler-rt support libs are too old). Change-Id: Icc444936caa852bfb9a02b37223209319a27a770 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-22 18:26:21 +00:00
# zero out coverage data
autotest.sh: save lcov files in output_dir Coverage and ut_coverage files would get created in spdk dir or in directory from which the autotest.sh was called. Use $output_dir provided by autotest_common.sh instead to keep all build artifacts in common place. Signed-off-by: Karol Latecki <karol.latecki@intel.com> Change-Id: Iaf009182441933cb5e9bd137d0c94078272dd749 Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1134 Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-03-04 15:54:51 +00:00
$LCOV -q -c -i -t "Baseline" -d $src -o $out/cov_base.info
build: add CONFIG_COVERAGE code coverage option Collect coverage information for use with gcov. Coverage is disabled on FreeBSD because the current version of clang provided by FreeBSD can't successfully link with -ftest-coverage enabled (the compiler-rt support libs are too old). Change-Id: Icc444936caa852bfb9a02b37223209319a27a770 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-22 18:26:21 +00:00
fi
autotest: move NVMe device cleanup to startup Make sure any partition tables or other random data on the disks is cleaned up before running the tests, rather than trying to clean it up on failure when the system is in a potentially bad state. Change-Id: Ia2119485aee6a50243744328dff2314d7a72adad Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-08-15 17:43:53 +00:00
# Make sure the disks are clean (no leftover partition tables)
timing_enter cleanup
rpc: add default UNIX domain socket listen address RPC is a default feature required for almost all usages, so enable RPC by default, but with a UNIX domain socket for security reasons. -r can now be used from the command line to specify an alternative RPC listen address from the default /var/tmp/spdk.sock. Remove the Enable parameter from the Rpc config section but still allow specifying an alternative listen address using the Listen parameter as an alternative to the command line option. This keeps backward compatibility for this release for anyone using the configuration file still. Remove the Rpc sections from all configuration files that were using them, except for those that specified alternate TCP ports for multi-process test cases. We can fix these later to use an alternate UNIX domain socket and to use the command line instead. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ife0d03fcab638c67b659f1eb85348ddc2b55c4c4 Reviewed-on: https://review.gerrithub.io/386561 Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-11-09 23:33:29 +00:00
# Remove old domain socket pathname just in case
autotest.sh: add wildcard to RPC socket cleanup Match alternative UNIX domain socket names for tests that use more than one RPC socket. Change-Id: I45672adac098554080b836c61b79ffd28577f702 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/388677 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-11-22 19:10:29 +00:00
rm -f /var/tmp/spdk*.sock
autotest: move NVMe device cleanup to startup Make sure any partition tables or other random data on the disks is cleaned up before running the tests, rather than trying to clean it up on failure when the system is in a potentially bad state. Change-Id: Ia2119485aee6a50243744328dff2314d7a72adad Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-08-15 17:43:53 +00:00
test: erase the first 1MB on NVMe disks at the start of each test Some tests intermittently fail due to leftover lvols from previous runs: $ hello_bdev -b Nvme0n1 *ERROR*: Could not open Nvme0n1 - lvol module already claimed it Fix this by zeroing the first 1MB of each NVMe at the start of autotest. That will remove the lvolstore, and will get also rid of any GPT partitions - that's why this patch also removes the explicit `parted` calls that would try to do the same. Since there's no way to do direct I/O with the standard dd shipped in FreeBSD, we do the `sync` after the normal, buffered dd. Change-Id: I18a01bda064f836901327f1dd3cfab1f08e87b1a Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/435086 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-11-27 08:43:56 +00:00
# Load the kernel driver
./scripts/setup.sh reset
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
if [ $(uname -s) = Linux ]; then
# OCSSD devices drivers don't support IO issues by kernel so
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
# detect OCSSD devices and block them (unbind from any driver).
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
# If test scripts want to use this device it needs to do this explicitly.
#
# If some OCSSD device is bound to other driver than nvme we won't be able to
# discover if it is OCSSD or not so load the kernel driver first.
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
while IFS= read -r -d '' dev; do
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
# Send Open Channel 2.0 Geometry opcode "0xe2" - not supported by NVMe device.
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
if nvme admin-passthru $dev --namespace-id=1 --data-len=4096 --opcode=0xe2 --read > /dev/null; then
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
bdf="$(basename $(readlink -e /sys/class/nvme/${dev#/dev/}/device))"
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
echo "INFO: blocking OCSSD device: $dev ($bdf)"
PCI_BLOCKED+=" $bdf"
test/ftl: use OCSSD instead first NVMe like Change-Id: I175bebb68ea1752fda6fe80932cd27c30cf3dcff Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/443737 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-07 10:35:21 +00:00
OCSSD_PCI_DEVICES+=" $bdf"
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
fi
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
done < <(find /dev -maxdepth 1 -regex '/dev/nvme[0-9]+' -print0)
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
test/ftl: use OCSSD instead first NVMe like Change-Id: I175bebb68ea1752fda6fe80932cd27c30cf3dcff Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/443737 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-07 10:35:21 +00:00
export OCSSD_PCI_DEVICES
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
# Now, bind blocked devices to pci-stub module. This will prevent
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
# automatic grabbing these devices when we add device/vendor ID to
# proper driver.
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
if [[ -n "$PCI_BLOCKED" ]]; then
test: Shellcheck - apply rule SC2097 and SC2098 SC2097: This assignment is only seen by the forked process. SC2098: This expansion will not see the mentioned assignment. Apply these two rules together as they point to the same code. Change-Id: I61020e8fd4b6db2b06ae8134d1004290a9bef9e7 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476777 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-12-04 14:44:12 +00:00
# shellcheck disable=SC2097,SC2098
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
PCI_ALLOWED="$PCI_BLOCKED" \
PCI_BLOCKED="" \
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
DRIVER_OVERRIDE="pci-stub" \
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
./scripts/setup.sh
scripts: replace PCI_WHITELIST with PCI_ALLOWED Similarly replace PCI_BLACKLIST with PCI_BLOCKED. Use of ALLOWED/BLOCKED matches similar changes made in DPDK. While here, replace use of term "blacklist" with "blocked" in one of the nvme perf scripts. The usage there was associated with how devices are blocked by using the environment variables that are changed by this patch. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I720d99118ba5e050f436612c9fd415db44294a63 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5275 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2020-11-25 20:31:42 +00:00
# Export our blocked list so it will take effect during next setup.sh
export PCI_BLOCKED
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
fi
test/setup: Add initital tests for setup.sh 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>
2020-11-27 08:22:54 +00:00
run_test "setup.sh" "$rootdir/test/setup/test-setup.sh"
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
fi
test/setup: Add initital tests for setup.sh 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>
2020-11-27 08:22:54 +00:00
./scripts/setup.sh status
autotest: Call nvme_namespace_revert() only under Linux This routine depends on nvme-cli which on FreeBSD can be installed only through ports - this operation is not supported by SPDK's provisioning tooling, like pkgdep.sh or vm_setup.sh. Considering that, it's unlikely that working nvme tool will be available on generic FreeBSD system, thus skip this work entirely. Change-Id: Ib2f12a65b6f000f1b4d9d3beda6b349685f263c7 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4670 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-10-14 12:36:37 +00:00
if [[ $(uname -s) == Linux ]]; then
# Revert NVMe namespaces to default state
nvme_namespace_revert
fi
test/cuse: revert NVMe namespaces to default state If for any reason the cuse tests do not revert state of NVMe namespaces to the original state, the test machines would be stuck in until manual intervention. Assumed default state is single namespace, encompassing available space formatted as 4k block size. This patch adds nvme_namespace_revert(), which searches for NVMe devices that support Namespace Managment and have some space unallocated. When such device is found, all existing namespaces are removed and single one created. Fix #1435 Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ifc3b04b3f166bf450b884674fa6a482e2fbc4c29 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2829 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2020-06-08 07:18:32 +00:00
test: erase the first 1MB on NVMe disks at the start of each test Some tests intermittently fail due to leftover lvols from previous runs: $ hello_bdev -b Nvme0n1 *ERROR*: Could not open Nvme0n1 - lvol module already claimed it Fix this by zeroing the first 1MB of each NVMe at the start of autotest. That will remove the lvolstore, and will get also rid of any GPT partitions - that's why this patch also removes the explicit `parted` calls that would try to do the same. Since there's no way to do direct I/O with the standard dd shipped in FreeBSD, we do the `sync` after the normal, buffered dd. Change-Id: I18a01bda064f836901327f1dd3cfab1f08e87b1a Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/435086 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-11-27 08:43:56 +00:00
# Delete all leftover lvols and gpt partitions
# Matches both /dev/nvmeXnY on Linux and /dev/nvmeXnsY on BSD
autotest: blacklist OCSSD devices Detect and blacklist OCSSD devices by unbinding the driver. Change-Id: I7ba6cefd083a7d3ead6db27fa27a765f8ee52402 Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/442978 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-02-01 09:26:39 +00:00
# Filter out nvme with partitions - the "p*" suffix
test: erase the first 1MB on NVMe disks at the start of each test Some tests intermittently fail due to leftover lvols from previous runs: $ hello_bdev -b Nvme0n1 *ERROR*: Could not open Nvme0n1 - lvol module already claimed it Fix this by zeroing the first 1MB of each NVMe at the start of autotest. That will remove the lvolstore, and will get also rid of any GPT partitions - that's why this patch also removes the explicit `parted` calls that would try to do the same. Since there's no way to do direct I/O with the standard dd shipped in FreeBSD, we do the `sync` after the normal, buffered dd. Change-Id: I18a01bda064f836901327f1dd3cfab1f08e87b1a Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/435086 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-11-27 08:43:56 +00:00
for dev in $(ls /dev/nvme*n* | grep -v p || true); do
dd if=/dev/zero of="$dev" bs=1M count=1
done
autotest.sh: load block RAM disk module This provides /dev/ram0 when available so that we can have a convenient blcok disk to test the Linux AIO backend against. Change-Id: I557dae4dcba918838f55f85cd5981922d765d40e Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/385297 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-11-01 20:08:50 +00:00
test: erase the first 1MB on NVMe disks at the start of each test Some tests intermittently fail due to leftover lvols from previous runs: $ hello_bdev -b Nvme0n1 *ERROR*: Could not open Nvme0n1 - lvol module already claimed it Fix this by zeroing the first 1MB of each NVMe at the start of autotest. That will remove the lvolstore, and will get also rid of any GPT partitions - that's why this patch also removes the explicit `parted` calls that would try to do the same. Since there's no way to do direct I/O with the standard dd shipped in FreeBSD, we do the `sync` after the normal, buffered dd. Change-Id: I18a01bda064f836901327f1dd3cfab1f08e87b1a Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/435086 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-11-27 08:43:56 +00:00
sync
autotest: move NVMe device cleanup to startup Make sure any partition tables or other random data on the disks is cleaned up before running the tests, rather than trying to clean it up on failure when the system is in a potentially bad state. Change-Id: Ia2119485aee6a50243744328dff2314d7a72adad Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-08-15 17:43:53 +00:00
timing_exit cleanup
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
# set up huge pages
timing_enter afterboot
Add vfio support to scripts. cleanup.sh and unbind.sh have been combined into a single setup.sh that takes one optional parameter (reset). If no parameter is given, the script will automatically bind all NVMe and IOAT devices to either uio_pci_generic or vfio-pci, as appropriate based on IOMMU settings. If the reset parameter is given, the devices will be bound back to the appropriate kernel drivers. Change-Id: I25db3234f1ecfb352a281e5093f4c1aa455152ae Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-02-19 21:11:08 +00:00
./scripts/setup.sh
autotest: add timing enter/exit for setup/cleanup Change-Id: I5367f3d11db016674b4bc0e77fd81bf363c2e55c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-03-07 22:11:36 +00:00
timing_exit afterboot
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
bdev/compress: prepare to add some unit tests Misc cleanup from earlier patches, some naming issues and other minor things that are needed before adding UT. Change-Id: Ic76f0e2fd12e48782b048fb8785902b1098cf352 Signed-off-by: paul luse <paul.e.luse@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/436227 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-12-05 23:35:02 +00:00
if [[ $SPDK_TEST_CRYPTO -eq 1 || $SPDK_TEST_REDUCE -eq 1 ]]; then
autotest: Distribute memory evenly across NUMA nodes for crypto tests This is needed in case QAT devices and their VFs end up on different node than node0. Change-Id: I34386c71dff6232e191a8625a7f26c90ea2cad6d Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5464 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2020-12-07 12:15:41 +00:00
# Make sure that memory is distributed across all NUMA nodes - by default, all goes to
# node0, but if QAT devices are attached to a different node, all of their VFs will end
# up under that node too and memory needs to be available there for the tests.
CLEAR_HUGE=yes HUGE_EVEN_ALLOC=yes ./scripts/setup.sh
./scripts/setup.sh status
configure: remove --with-igb-uio-driver option DPDK 20.11 moved the kernel modules to separate dpdk-kmod repository. It has to be built separate from DPDK. If needed for testing vm_setup.sh script now contains option to build this driver. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I98a5eb956eb0cc60ec402d88fcdbd66d4854f19a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6033 Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-01-21 14:36:10 +00:00
if [[ $SPDK_TEST_USE_IGB_UIO -eq 1 ]]; then
scripts: add a qat card setup script This script should be called when testing the crypto module. It will configure any qat cards with class code 37c8 for use with the spdk crypto bdev module. Change-Id: I233069fbe9ba3c7a6463f52443234f9fe2c9a1f7 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/428549 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-10-09 18:26:27 +00:00
./scripts/qat_setup.sh igb_uio
else
./scripts/qat_setup.sh
fi
fi
test/opal: Enable OPAL test Also add opal_revert_cleanup at the start of autotest.sh because opal test might fail before revert and the drive might be kept locked and will cause deny of service in later test. Change-Id: Icb9d571c59804daa559784cee457c7e804eff121 Signed-off-by: Chunyang Hui <chunyang.hui@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/471973 Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-22 15:12:35 +00:00
# Revert existing OPAL to factory settings that may have been left from earlier failed tests.
# This ensures we won't hit any unexpected failures due to NVMe SSDs being locked.
test/nvme: enable OPAL test Due to the firmware response time for REVERT action, currently we only enable this test with P4510 drives. Change-Id: I4b02008ec0b7d2caeba20c566b1cf1b69404ae12 Signed-off-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2816 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-09 09:22:41 +00:00
opal_revert_cleanup
test/opal: Enable OPAL test Also add opal_revert_cleanup at the start of autotest.sh because opal test might fail before revert and the drive might be kept locked and will cause deny of service in later test. Change-Id: Icb9d571c59804daa559784cee457c7e804eff121 Signed-off-by: Chunyang Hui <chunyang.hui@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/471973 Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-22 15:12:35 +00:00
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
#####################
# Unit Tests
#####################
autotest.sh: add test config flag for unittest.sh Change-Id: I01b3e9243674b349dda42df896f7332d168f940f Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/362390 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2017-05-24 16:25:45 +00:00
if [ $SPDK_TEST_UNITTEST -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "unittest" ./test/unit/unittest.sh
move env.sh test under unittest label. The env tests are actually mainly unit tests and they can't run against shared objects because we don't build unittests with shared objects. Signed-off-by: Seth Howell <seth.howell@intel.com> Change-Id: I0eb1f8cc071539881a545f4e2c36559a825a36fc Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2981 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-19 23:14:41 +00:00
run_test "env" test/env/env.sh
autotest.sh: add test config flag for unittest.sh Change-Id: I01b3e9243674b349dda42df896f7332d168f940f Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/362390 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2017-05-24 16:25:45 +00:00
fi
autotest: run unittest.sh Verify that the unit test script run by Travis CI works in the autotest environment. This duplicates some of the current tests - that will be cleaned up in a future commit. Change-Id: Icca60dee3348e2675492b9c6294de6aa094b3375 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2017-01-24 22:47:46 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_RUN_FUNCTIONAL_TEST -eq 1 ]; then
timing_enter lib
autorun: add per-agent test configurations Allow agents to selectively enable which tests they run in an optional file, ~/autorun-spdk.conf. Change-Id: I52440884cbe599aeb1270dc4f6ee85f5acb9a0c2 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Signed-off-by: Seth Howell <seth.howell@intel.com>
2017-03-08 19:17:32 +00:00
scripts/rpc.py: add daemon mode Add rpc_cmd() bash command that sends rpc command to an rpc.py instance permanently running in background. This makes sending RPC commands even 17 times faster. We make use of bash coprocesses - a builtin bash feature that allow starting background processes with stdin and stdout connected to pipes. rpc.py will block trying to read stdin, effectively being always "ready" to read an RPC command. The background rpc.py is started with a new --server flag that's described as: > Start listening on stdin, parse each line as a regular > rpc.py execution and create a separate connection for each command. > Each command's output ends with either **STATUS=0 if the > command succeeded or **STATUS=1 if it failed. > --server is meant to be used in conjunction with bash > coproc, where stdin and stdout are named pipes and can be > used as a faster way to send RPC commands. As a part of this patch I'm attaching a sample test that runs the following rpc commands first with the regular rpc.py, then the new rpc_cmd() function. ``` time { bdevs=$($rpc bdev_get_bdevs) [ "$(jq length <<< "$bdevs")" == "0" ] malloc=$($rpc bdev_malloc_create 8 512) bdevs=$($rpc bdev_get_bdevs) [ "$(jq length <<< "$bdevs")" == "1" ] $rpc bdev_passthru_create -b "$malloc" -p Passthru0 bdevs=$($rpc bdev_get_bdevs) [ "$(jq length <<< "$bdevs")" == "2" ] $rpc bdev_passthru_delete Passthru0 $rpc bdev_malloc_delete $malloc bdevs=$($rpc bdev_get_bdevs) [ "$(jq length <<< "$bdevs")" == "0" ] } ``` Regular rpc.py: ``` real 0m1.477s user 0m1.289s sys 0m0.139s ``` rpc_cmd(): ``` real 0m0.085s user 0m0.025s sys 0m0.006s ``` autotest_common.sh will now spawn an rpc.py daemon if it's not running yet, and it will offer rpc_cmd() function to quickly send RPC commands. If the command is invalid or SPDK returns with error, the bash function will return a non-zero code and may trigger ERR trap just like a regular rpc.py instance. Pipes have major advantage over e.g. unix domain sockets - the pipes will be automatically closed once the owner process exits. This means we can create a named pipe in autotest_common.sh, open it, then start rpc.py in background and never worry about it again - it will be closed automatically once the test exits. It doesn't even matter if the test is executed manually in isolation, or as a part of the entire autotest. (check_so_deps.sh needs to be modified not to wait for *all* background processes to finish, but just the ones it started) Change-Id: If0ded961b7fef3af3837b44532300dee8b5b4663 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Signed-off-by: Michal Berger <michalx.berger@intel.com> Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/621 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-06-21 07:38:47 +00:00
run_test "rpc" test/rpc/rpc.sh
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "rpc_client" test/rpc_client/rpc_client.sh
run_test "json_config" ./test/json_config/json_config.sh
run_test "alias_rpc" test/json_config/alias_rpc/alias_rpc.sh
run_test "spdkcli_tcp" test/spdkcli/tcp.sh
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
run_test "dpdk_mem_utility" test/dpdk_memory_utility/test_dpdk_mem_info.sh
test: remove SPDK_TEST_EVENT flag Test in event.sh take 5 seconds on CI at this time. For the tests to run both SPDK_RUN_FUNCTIONAL_TEST and SPDK_TEST_EVENT had to be enabled. This served as very minor time saver, so removing this flag shouldn't affter test times more that the 5 seconds. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ie3eaa587daf28b2efbc3cfdff5ad648b7529e7f1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1493 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-03-26 13:30:52 +00:00
run_test "event" test/event/event.sh
accel_engine test: Add the test case for accel_engine. This patch is used to create a script to test the accel_engine. It can be used to test both software/hardware approach in acccel_engine. The first usage case is to add the crc32c test. More cases can be added later. Signed-off-by: Ziye Yang <ziye.yang@intel.com> Change-Id: I9f7564e39887265f8bbfce3a15ba446fbd7a14bd Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5974 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-01-19 11:25:41 +00:00
run_test "accel_engine" test/accel_engine/accel_engine.sh
scripts: add config converter Add a new script to enable converting old INI config files to the new JSON-RPC config file format. This prepares for deprecating the INI config file file format in the future. Change-Id: I0f2bfa9a585ce3537772b662d8e4028ab08a554d Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/420457 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2018-07-26 01:32:05 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_BLOCKDEV -eq 1 ]; then
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
run_test "blockdev_general" test/bdev/blockdev.sh
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "bdev_raid" test/bdev/bdev_raid.sh
test/bdevperf: test config file Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I6a92345e1c3fae1f7f8b77bc68e0f715e7ac9ed9 Signed-off-by: Vitaliy Mysak <vitaliy.mysak@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3291 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-07-10 12:15:45 +00:00
run_test "bdevperf_config" test/bdev/bdevperf/test_config.sh
test/dd: Add basic tests for spdk_dd Change-Id: I78df1a70bc16d4a3f8c11386c3c78a5f0ff12394 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2898 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-15 14:14:28 +00:00
if [[ $(uname -s) == Linux ]]; then
test: add functional test for reactor_set_intr test script 'test/interrupt/reactor_set_intr.sh' will do various reactor set intr operations on interrupt_tgt without spdk_thread and with spdk_thread. Change-Id: Ie5af1dc68b0272c34a91e8a66b78088c3794907c Signed-off-by: Liu Xiaodong <xiaodong.liu@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7348 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-01-15 14:47:43 +00:00
run_test "reactor_set_interrupt" test/interrupt/reactor_set_interrupt.sh
test/dd: Add basic tests for spdk_dd Change-Id: I78df1a70bc16d4a3f8c11386c3c78a5f0ff12394 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2898 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-15 14:14:28 +00:00
fi
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
autorun: add per-agent test configurations Allow agents to selectively enable which tests they run in an optional file, ~/autorun-spdk.conf. Change-Id: I52440884cbe599aeb1270dc4f6ee85f5acb9a0c2 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Signed-off-by: Seth Howell <seth.howell@intel.com>
2017-03-08 19:17:32 +00:00
autotest: Run dd tests under SPDK_TEST_URING As these tests were limited to SPDK_TEST_BLOCKBDEV the spdk_dd was not being tested against liburing. Make sure it is the case now. Also, fail the test if spdk_dd is not linked to liburing in case where such tests were requested. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I5704577530048ed4775ea15a6cdacf23380b5072 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7653 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2021-04-28 09:45:44 +00:00
if [[ $(uname -s) == Linux ]]; then
if [[ $SPDK_TEST_BLOCKDEV -eq 1 || $SPDK_TEST_URING -eq 1 ]]; then
run_test "spdk_dd" test/dd/dd.sh
fi
fi
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_JSON -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "test_converter" test/config_converter/test_converter.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
autorun: add per-agent test configurations Allow agents to selectively enable which tests they run in an optional file, ~/autorun-spdk.conf. Change-Id: I52440884cbe599aeb1270dc4f6ee85f5acb9a0c2 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Signed-off-by: Seth Howell <seth.howell@intel.com>
2017-03-08 19:17:32 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_NVME -eq 1 ]; then
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
run_test "blockdev_nvme" test/bdev/blockdev.sh "nvme"
run_test "blockdev_nvme_gpt" test/bdev/blockdev.sh "gpt"
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "nvme" test/nvme/nvme.sh
examples/pmr_persistence: Add PMR example application Added tests to verify the PMR support. Signed-off-by: Krishna Kanth Reddy <krish.reddy@samsung.com> Change-Id: I63f0a18647bfb8b16b8a5fbedb902c2f28b1d36d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6562 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-02-25 11:21:04 +00:00
if [[ $SPDK_TEST_NVME_PMR -eq 1 ]]; then
run_test "nvme_pmr" test/nvme/nvme_pmr.sh
fi
test/nvme: Add test application to verify Simple Copy Command support Signed-off-by: Krishna Kanth Reddy <krish.reddy@samsung.com> Change-Id: I7bf61d98c444b473ec73f6afaf31ac408af6e409 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/7696 Community-CI: Broadcom CI Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2021-04-30 09:26:21 +00:00
if [[ $SPDK_TEST_NVME_SCC -eq 1 ]]; then
run_test "nvme_scc" test/nvme/nvme_scc.sh
fi
lib/nvme: nvme character device tests This patch adds new script to verify CUSE functionality for NVMe devices: 1) Starts spdk_tgt application 2) Attaches first found controller 3) Enables NVMe cuse devices for a controller and namespaces 4) Retrieves CUSE device names for controller and namespaces 4) Tests operations on exposed namespace devices 5) Tests operations on controller devices NOTE: These tests requires at least one NVMe device with at least one namespace available. Change-Id: I5f5a7c86f8aefa73f12f4727f7520f16a599985b Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468828 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-24 18:11:51 +00:00
if [[ $SPDK_TEST_NVME_CUSE -eq 1 ]]; then
test/cuse: move all nvme-cuse tests under single script This will help with managing the test execution and preparation. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I0bd3612381d031a4015335d162f1296fd6dd213d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2823 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2020-06-08 11:42:52 +00:00
run_test "nvme_cuse" test/nvme/cuse/nvme_cuse.sh
lib/nvme: nvme character device tests This patch adds new script to verify CUSE functionality for NVMe devices: 1) Starts spdk_tgt application 2) Attaches first found controller 3) Enables NVMe cuse devices for a controller and namespaces 4) Retrieves CUSE device names for controller and namespaces 4) Tests operations on exposed namespace devices 5) Tests operations on controller devices NOTE: These tests requires at least one NVMe device with at least one namespace available. Change-Id: I5f5a7c86f8aefa73f12f4727f7520f16a599985b Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468828 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-24 18:11:51 +00:00
fi
test/nvme: nvme_rpc add test for bdev_nvme_apply_firmware This patch introduces tests for basic RPC commands not used in other tests: bdev_nvme_apply_firmware Change-Id: I3a7aff1720108548b03d581fa7664d1ff5498be5 Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/533 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-01-28 14:39:52 +00:00
run_test "nvme_rpc" test/nvme/nvme_rpc.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
# Only test hotplug without ASAN enabled. Since if it is
# enabled, it catches SEGV earlier than our handler which
# breaks the hotplug logic.
test/nvme: re-enable nvme hotplug test New VM image for nvme hotplug tests was crafted, test can be re-enabled. Fixes #524 Change-Id: Ie7e5e063cd94f2d1cad4b0826f1a51fb43577e6c Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468807 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-09-19 10:46:21 +00:00
if [ $SPDK_RUN_ASAN -eq 0 ]; then
Modifications for using universal qcow2 image in tests We want to replace few qcow2 images with one universal. This commit contains: - change password in autotest.sh - change image path - change image name - use snapshot mode in hotplug.sh instead of copying base image Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: I75c457fe75f005b0ab43ca909be7886529ed115b Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4551 Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Pawel Piatek <pawelx.piatek@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot
2020-10-07 14:16:34 +00:00
run_test "nvme_hotplug" test/nvme/hotplug.sh root
test/nvme: re-enable nvme hotplug test New VM image for nvme hotplug tests was crafted, test can be re-enabled. Fixes #524 Change-Id: Ie7e5e063cd94f2d1cad4b0826f1a51fb43577e6c Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468807 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-09-19 10:46:21 +00:00
fi
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_IOAT -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "ioat" test/ioat/ioat.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
timing_exit lib
iscsi: Add an iscsi target application Similar to our NVMf target, this is an iSCSI target that can interoperate with the Linux and Windows standard iSCSI initiators. Change-Id: I6961c5ef99f7b161c396330ed5b543ea29b0ca7b Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-08-03 21:37:16 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_ISCSI -eq 1 ]; then
test/iscsi: remove VPP tests All VPP tests were the same tests as usual posix iSCSI tests. TEST_TYPE was used to direct which tests to run and in some cases with what parameter. Since VPP is deprecated, this type of selection is no longer needed. All tests will run with default socket abstraction. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I292f1b5141ec8c4dacb4a43c6f51e4d30501a92a Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3730 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2020-08-11 10:36:11 +00:00
run_test "iscsi_tgt" ./test/iscsi_tgt/iscsi_tgt.sh
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "spdkcli_iscsi" ./test/spdkcli/iscsi.sh
spdkcli: Add support for raid devices Adds support to spdkcli.py for raid devices via UIRaidBdev with functionality to construct and destroy raid bdevs. Information regarding the raid can be viewed via 'show_details' on a given pooled_device child in the tree. Signed-off-by: Mike Carlin <mikefcarlin@protonmail.com> Change-Id: I2ca89e641b201c09b3d4db070eac6cc0c2cdec73 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452774 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-04-26 17:30:50 +00:00
# Run raid spdkcli test under iSCSI since blockdev tests run on systems that can't run spdkcli yet
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "spdkcli_raid" test/spdkcli/raid.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
blobfs: Add a lightweight filesystem built on the blobstore This is the initial commit for "blobfs", a lightweight filesystem built on top of the SPDK blobstore. Also included in this patch: 1) a shim for using SPDK bdevs as the backing store for SPDK blobstore/blobfs 2) documentation for using blobfs as the storage engine with RocksDB 3) scripts for running a set of workloads and collecting profiling data with RocksDB and blobfs See doc/blobfs/getting_started.md included in this commit for more details on blobfs, including some of the current limitations. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I2a6d3d4b87236730051228ed62c0c04e04c42c73
2017-03-22 20:35:00 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_BLOBFS -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "rocksdb" ./test/blobfs/rocksdb/rocksdb.sh
run_test "blobstore" ./test/blobstore/blobstore.sh
run_test "blobfs" ./test/blobfs/blobfs.sh
build: Example applications build to build/example This mirrors build/bin and build/lib Change-Id: Ide1d17dfc8b425adfbe67f381c93c236653bd301 Signed-off-by: Ben Walker <benjamin.walker@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2380 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com>
2020-05-11 22:02:01 +00:00
run_test "hello_blob" $SPDK_EXAMPLE_DIR/hello_blob \
example/hello_blob: Drop .ini config in favor of json Change-Id: Iea222f4ef072676cbb5e9014a7d98ac08a4e617a Signed-off-by: WANGHAILIANG <hailiangx.e.wang@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2967 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2020-06-19 09:01:54 +00:00
examples/blob/hello_world/hello_blob.json
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
nvmf: add automated fio and mkfs tests Change-Id: I499ae29155b8f053babf18750cecb5c8d210d59c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-06-07 15:49:44 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_NVMF -eq 1 ]; then
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
# The NVMe-oF run test cases are split out like this so that the parser that compiles the
# list of all tests can properly differentiate them. Please do not merge them into one line.
if [ "$SPDK_TEST_NVMF_TRANSPORT" = "rdma" ]; then
autotest.sh: call rdma_device_init only for RDMA tests Check test flags before calling rdma_device_init if it's really needed, so that we don't call it when doing TCP tests. Change-Id: I2675a008cf84c7c4084cb83b44c279d2a497c3cb Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6998 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-03-22 16:51:26 +00:00
timing_enter rdma_setup
rdma_device_init
timing_exit rdma_setup
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
run_test "nvmf_rdma" ./test/nvmf/nvmf.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
autotest.sh: call rdma_device_init only for RDMA tests Check test flags before calling rdma_device_init if it's really needed, so that we don't call it when doing TCP tests. Change-Id: I2675a008cf84c7c4084cb83b44c279d2a497c3cb Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6998 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-03-22 16:51:26 +00:00
run_test "spdkcli_nvmf_rdma" ./test/spdkcli/nvmf.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
elif [ "$SPDK_TEST_NVMF_TRANSPORT" = "tcp" ]; then
test/nvmf_tcp: allow tcp cases running in E810 NIC instead of virtual eth Added nvmf_tcp_init() to run tcp through physical E810 network card. If there is not E810 in system, tcp will still run on virtual eth. Change-Id: I9a983c92175b27c45457682d42d72ef307fef260 Signed-off-by: wanghailiangx <hailiangx.e.wang@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6932 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: GangCao <gang.cao@intel.com> Reviewed-by: <qun.wan@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Michal Berger <michalx.berger@intel.com> Reviewed-by: Ziye Yang <ziye.yang@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com>
2021-03-18 13:31:27 +00:00
timing_enter tcp_setup
tcp_device_init
timing_exit tcp_setup
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
run_test "nvmf_tcp" ./test/nvmf/nvmf.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
autotest.sh: call rdma_device_init only for RDMA tests Check test flags before calling rdma_device_init if it's really needed, so that we don't call it when doing TCP tests. Change-Id: I2675a008cf84c7c4084cb83b44c279d2a497c3cb Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/6998 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2021-03-22 16:51:26 +00:00
run_test "spdkcli_nvmf_tcp" ./test/spdkcli/nvmf.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
lib/nvmf: Functional test for custom admin cmd handler This test verifies the custom identify handler functionality by querying the NVMe drive and comparing serial and model number from the NVMe drive with the corresponding info from the NVMF identify result. Signed-off-by: Michael Haeuptle <michael.haeuptle@hpe.com> Change-Id: I9d4edb1bf32550cbf5fbd45cbfa85f9afc408fc0 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/481910 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-01-16 22:27:01 +00:00
run_test "nvmf_identify_passthru" test/nvmf/target/identify_passthru.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
test/nvmf: Add tests covering usage of DIF Change-Id: I95eedb1bc21e296113d7f5853ab286d966adf1b8 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5568 Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Community-CI: Broadcom CI Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-12-14 15:54:12 +00:00
run_test "nvmf_dif" test/nvmf/target/dif.sh
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
elif [ "$SPDK_TEST_NVMF_TRANSPORT" = "fc" ]; then
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
run_test "nvmf_fc" ./test/nvmf/nvmf.sh --transport=$SPDK_TEST_NVMF_TRANSPORT
run_test "spdkcli_nvmf_fc" ./test/spdkcli/nvmf.sh
test: differentiate between different nvmf transports. We have to do this explicitly so that the list of completed tests that comes out at the end is explicit as well. Change-Id: Ic89357f2ebd89ea80f00010a78b2a2ad05b22591 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476963 Community-CI: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2019-12-05 23:43:36 +00:00
else
echo "unknown NVMe transport, please specify rdma, tcp, or fc."
exit 1
fi
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
test/lvol: Add lvol tasting test Add lvol tasting positive test case. Adding new autotest config option for better control where test is executed Change-Id: Ic08b2395bd14e15072711b97c77b7e1ce26dd2b7 Signed-off-by: Lukasz Galka <lukaszx.galka@intel.com> Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.gerrithub.io/383432 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2017-10-23 15:03:18 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_VHOST -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "vhost" ./test/vhost/vhost.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
vhost: add a library and app for userspace vhost-scsi processing This patch adds a library, application and test scripts for extending SPDK to present virtio-scsi controllers to QEMU-based VMs and process I/O submitted to devices attached to those controllers. This functionality is dependent on QEMU patches to enable vhost-scsi in userspace - those patches are currently working their way through the QEMU mailing list, but temporary patches to enable this functionality in QEMU will be made available shortly through the SPDK github repository. Signed-off-by: Jim Harris <james.r.harris@intel.com> Signed-off-by: Krzysztof Jakimiak <krzysztof.jakimiak@intel.com> Signed-off-by: Michal Kosciowski <michal.kosciowski@intel.com> Signed-off-by: Karol Latecki <karolx.latecki@intel.com> Signed-off-by: Piotr Pelplinski <piotr.pelplinski@intel.com> Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Signed-off-by: Krzysztof Jakimiak <krzysztof.jakimiak@intel.com> Change-Id: I138e4021f0ac4b1cd9a6e4041783cdf06e6f0efb
2017-03-02 14:12:20 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_LVOL -eq 1 ]; then
test/lvol: rename lvol test script After the large effort of moving lvol tests from python to bash, the original lvol.sh was removed. Only lvol2.sh remained. Just rename the script to its original name. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I5c0a239b01c111f0b11f554caaebfec372877c6d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4561 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2020-10-08 12:08:56 +00:00
run_test "lvol" ./test/lvol/lvol.sh
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "blob_io_wait" ./test/blobstore/blob_io_wait/blob_io_wait.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
test/vhost: Fio tests for vhost initiator. Change-Id: Iad11eef12c0f7f80c26264f65a38df798eae1a27 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/378071 Reviewed-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2017-09-12 13:47:30 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_VHOST_INIT -eq 1 ]; then
timing_enter vhost_initiator
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "vhost_blockdev" ./test/vhost/initiator/blockdev.sh
run_test "spdkcli_virtio" ./test/spdkcli/virtio.sh
run_test "vhost_shared" ./test/vhost/shared/shared.sh
run_test "vhost_fuzz" ./test/vhost/fuzz/fuzz.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
timing_exit vhost_initiator
fi
test/pmem: RPC pmem functional tests. Functional pmem tests according to test plan: https://review.gerrithub.io/#/c/378618/18/test/pmem/test_plan.md Change-Id: Ia4594fe96a542c654656d2a6d2fed18eb1c2fcf7 Signed-off-by: Pawel Niedzwiecki <pawelx.niedzwiecki@intel.com> Reviewed-on: https://review.gerrithub.io/379972 Reviewed-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-by: Piotr Pelpliński <piotr.pelplinski@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
2017-09-26 13:02:52 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_PMDK -eq 1 ]; then
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
run_test "blockdev_pmem" ./test/bdev/blockdev.sh "pmem"
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "pmem" ./test/pmem/pmem.sh -x
run_test "spdkcli_pmem" ./test/spdkcli/pmem.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
test/json: Add rbd bdev test Change-Id: I8d8b252bf826e6339810ccf27a4c68ed6a726af9 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/417603 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-07-03 01:37:42 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_RBD -eq 1 ]; then
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
run_test "blockdev_rbd" ./test/bdev/blockdev.sh "rbd"
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "spdkcli_rbd" ./test/spdkcli/rbd.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
OCF: tests: add integrity test Add SPDK_TEST_CAS suite Add basic integrity test with multithread-multidevice fio with cache modes WT and PT Change-Id: If2916558894d9f7efd9628eb99f7338c90b312b1 Signed-off-by: Vitaliy Mysak <vitaliy.mysak@intel.com> Reviewed-on: https://review.gerrithub.io/c/439346 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
2018-11-02 00:00:24 +00:00
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
if [ $SPDK_TEST_OCF -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "ocf" ./test/ocf/ocf.sh
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
bdev_ftl: Added FTL bdev functional tests This patch introduces functional tests for FTL bdev. The tests cover various I/O workflows and check data integrity. Several scripts have been added to test the FTL library: * generate_config.sh - prepares configuration scripts for specified device * restore.sh - tests restoring device's state from the SSD * fio.sh - runs tests based on fio and fio_plugin The tests are run from autotest.sh when the SPDK_TEST_BDEV_FTL flag is set. Change-Id: I561d99ed35fe91eadd3756789cc99afe2da8c1db Signed-off-by: Mateusz Kozlowski <mateusz.kozlowski@intel.com> Signed-off-by: Wojciech Malikowski <wojciech.malikowski@intel.com> Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Reviewed-on: https://review.gerrithub.io/c/431330 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
2018-10-29 14:40:34 +00:00
lib/ftl: Functional tests This patch adjust functional tests to new FTL stack. Change-Id: I0b8ff08c61793d7f1685942031aecf9cc88d1f24 Signed-off-by: Wojciech Malikowski <wojciech.malikowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468738 Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
2019-10-25 07:31:14 +00:00
if [ $SPDK_TEST_FTL -eq 1 ]; then
run_test "ftl" ./test/ftl/ftl.sh
fi
test/vmd: Basic VMD tests Added basic tests for NVMe disks behind VMD. Change-Id: I9613ca4aa813bab16f4085ac809dbdc8028f1cfc Signed-off-by: Wojciech Malikowski <wojciech.malikowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/459639 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-06-27 14:49:26 +00:00
if [ $SPDK_TEST_VMD -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "vmd" ./test/vmd/vmd.sh
test/vmd: Basic VMD tests Added basic tests for NVMe disks behind VMD. Change-Id: I9613ca4aa813bab16f4085ac809dbdc8028f1cfc Signed-off-by: Wojciech Malikowski <wojciech.malikowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/459639 Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-06-27 14:49:26 +00:00
fi
autotest: move compress test to the end Currently the compression tests are run at the very beginning of autotest. If someone makes any change that breaks a generic SPDK component like RPC, he'll find errors in that compression tests and may have to wonder how he broke them without touching any compress code. To simplify root-causing and debugging, we want to start with the most basic tests like env.sh, rpc_client.sh, and blockdev.sh, so move the compress tests to the end. Change-Id: If6b33d6e24841379ccd8ff6489c38a4081381ce9 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/463850 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-08-01 04:27:15 +00:00
check_format: Reformat the Bash code in compliance with shfmt Change-Id: I93e7b9d355870b0528a0ac3382fba1a10a558d45 Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1718 Community-CI: Mellanox Build Bot Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-05-07 11:27:06 +00:00
if [ $SPDK_TEST_REDUCE -eq 1 ]; then
run_test "compress_qat" ./test/compress/compress.sh "qat"
run_test "compress_isal" ./test/compress/compress.sh "isal"
fi
test/opal: Enable OPAL test Also add opal_revert_cleanup at the start of autotest.sh because opal test might fail before revert and the drive might be kept locked and will cause deny of service in later test. Change-Id: Icb9d571c59804daa559784cee457c7e804eff121 Signed-off-by: Chunyang Hui <chunyang.hui@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/471973 Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-22 15:12:35 +00:00
if [ $SPDK_TEST_OPAL -eq 1 ]; then
test: eliminate case and suite from run_test We will be able to distinguish case and suite in the post process scripts based on if they have any internal tests. Change-Id: Iff2aa5caa251924d8a842085d87eb2a17aca45d4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478522 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-12-19 23:03:30 +00:00
run_test "nvme_opal" ./test/nvme/nvme_opal.sh
test/opal: Enable OPAL test Also add opal_revert_cleanup at the start of autotest.sh because opal test might fail before revert and the drive might be kept locked and will cause deny of service in later test. Change-Id: Icb9d571c59804daa559784cee457c7e804eff121 Signed-off-by: Chunyang Hui <chunyang.hui@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/471973 Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-10-22 15:12:35 +00:00
fi
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
if [ $SPDK_TEST_CRYPTO -eq 1 ]; then
test/bdev: Split crypto test and convert it to RPC calls Split is done based on the crypto driver type: - crypto_aesni - crypto_qat Change-Id: I47610eea7dd69defcbda9aa801a8bd8eeab820ee Signed-off-by: Michal Berger <michalx.berger@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1020 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-02-26 11:35:23 +00:00
run_test "blockdev_crypto_aesni" ./test/bdev/blockdev.sh "crypto_aesni"
# Proceed with the test only if QAT devices are in place
if [[ $(lspci -d:37c8) ]]; then
run_test "blockdev_crypto_qat" ./test/bdev/blockdev.sh "crypto_qat"
fi
test/blockdev: parameterize the blockdev tests. Now we can actually know which tests we are running on which bdevs when we call blockdev.sh. Removing the conditionals from the configuration setup (or failing if they don't succeed) and then calling run_test from the top level allows us to reliably track the bdev tests and fail if they don't run on a desired class of bdev. Change-Id: I14e6e3d993b4af4995adcbc5f138bac4ae9d63be Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478247 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-17 20:31:51 +00:00
fi
test/scheduler: Add test for verifying idle state This also introduces scheduler tests in the autotest pool. Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I892a2374e21dab0e349c655dcafaa4cc2e45fdc1 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5741 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-12-29 13:55:28 +00:00
if [[ $SPDK_TEST_SCHEDULER -eq 1 ]]; then
run_test "scheduler" ./test/scheduler/scheduler.sh
fi
autotest: introduce SPDK_RUN_FUNCTIONAL_TEST Introduced a new variable to run functional tests. It's enabled by default, and can be manually disabled on systems where e.g. only unit tests are run. SPDK_RUN_FUNCTIONAL_TEST is a supplement to SPDK_UNITTEST. The two are completely independent - both can be enabled, disabled, or run in any combination. The new variable is prefixed SPDK_RUN_ as it aligns nicely with SPDK_RUN_CHECK_FORMAT, SPDK_RUN_VALGRIND, and SPDK_RUN_ASAN, all of which control how much is tested. SPDK_UNITTEST should eventually follow the same pattern as well. This gives us 2 layers of configuration: SPDK_TEST_* <- what is tested SPDK_RUN_* <- how it is tested The following would run UT+ASAN for FTL and BlobFS, without running their functional tests: ``` SPDK_RUN_FUNCTIONAL_TEST=0 SPDK_RUN_ASAN=1 SPDK_TEST_UNITTEST=1 SPDK_TEST_FTL=1 SPDK_TEST_BLOBFS=1 ``` Change-Id: I9e592fa41aa2df8e246eca2bb9161b6da6832130 Signed-off-by: Seth Howell <seth.howell@intel.com> Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/c/442327 Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-01-28 12:21:57 +00:00
fi
test: consolidate tests for reading JSON config This patch rework all JSON config file reading tests. This is needed as current approach will require to modify each test to re-launch SPDK applications for each test type. This is hard to do because tests are not flexible and will require to be rewritten almost from scratch. Not metioning time to relaunch each test separatly. Instead, just replace all old tests with one test. Launch only one target and only one initiator. Then configure it using RPC calls. Then config is dumped and target and initiator application is relaunched to reread the configuration from file. Then config is dumped again and compared. Change-Id: Id857089aed0e6f2197cbf3ae625a4e9f4b13e8bb Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/c/432318 Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
2018-11-07 13:57:38 +00:00
autotest: add timing enter/exit for setup/cleanup Change-Id: I5367f3d11db016674b4bc0e77fd81bf363c2e55c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-03-07 22:11:36 +00:00
timing_enter cleanup
autotest.sh: create cleanup function This function consolidates cleanup behaviors that the pool should follow in the event of a failure. Change-Id: I8623f065146292b29a38eb199dcbeac5787723e7 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/401857 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-02-28 16:42:12 +00:00
autotest_cleanup
autotest: add timing enter/exit for setup/cleanup Change-Id: I5367f3d11db016674b4bc0e77fd81bf363c2e55c Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-03-07 22:11:36 +00:00
timing_exit cleanup
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
timing_exit autotest
chmod a+r $output_dir/timing.txt
autotest: capture core dumps on early exits Change-Id: Ic1bb518ecd8d5fba42c7f0b86cbf02524c262f0e Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-25 16:48:11 +00:00
trap - SIGINT SIGTERM EXIT
build: add automated build infrastructure Change-Id: Ie929debaaa74b0d8460b508199e842a244e090fa Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-09-21 21:48:40 +00:00
# catch any stray core files
process_core
build: add CONFIG_COVERAGE code coverage option Collect coverage information for use with gcov. Coverage is disabled on FreeBSD because the current version of clang provided by FreeBSD can't successfully link with -ftest-coverage enabled (the compiler-rt support libs are too old). Change-Id: Icc444936caa852bfb9a02b37223209319a27a770 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-22 18:26:21 +00:00
Disable lcov when using clang We want to add clang to autotest per patch, but lcov takes considerable time to process clang coverage. The test will be just building SPDK using clang. Details: https://github.com/spdk/spdk/issues/1693 Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: I085adb5498613222d36a0607b1fd260a2f4088b9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/5169 Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2020-11-19 10:47:05 +00:00
if hash lcov && ! [[ "$CC_TYPE" == *"clang"* ]]; then
build: add CONFIG_COVERAGE code coverage option Collect coverage information for use with gcov. Coverage is disabled on FreeBSD because the current version of clang provided by FreeBSD can't successfully link with -ftest-coverage enabled (the compiler-rt support libs are too old). Change-Id: Icc444936caa852bfb9a02b37223209319a27a770 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-22 18:26:21 +00:00
# generate coverage data and combine with baseline
autotest.sh: save lcov files in output_dir Coverage and ut_coverage files would get created in spdk dir or in directory from which the autotest.sh was called. Use $output_dir provided by autotest_common.sh instead to keep all build artifacts in common place. Signed-off-by: Karol Latecki <karol.latecki@intel.com> Change-Id: Iaf009182441933cb5e9bd137d0c94078272dd749 Signed-off-by: Karol Latecki <karol.latecki@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1134 Reviewed-by: Maciej Wawryk <maciejx.wawryk@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2020-03-04 15:54:51 +00:00
$LCOV -q -c -d $src -t "$(hostname)" -o $out/cov_test.info
$LCOV -q -a $out/cov_base.info -a $out/cov_test.info -o $out/cov_total.info
autotest: fix coverage pattern for removing DPDK Change-Id: I6d024eabbf72fb59084611df8f661f6b07ae3555 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/367733 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-06-30 16:58:21 +00:00
$LCOV -q -r $out/cov_total.info '*/dpdk/*' -o $out/cov_total.info
autotest: explicitly remove /usr from coverage The lcov --no-external option seems to still generate coverage data for e.g. /usr/include/c++/4.8.2/tuple on some test pool machines, contrary to the description of the option. Add an explicit removal of all /usr file coverage at the end of the test run to work around it. Change-Id: I8579813b1b76b4bfdef86748e88352bf232df954 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/369305 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-07-12 22:11:57 +00:00
$LCOV -q -r $out/cov_total.info '/usr/*' -o $out/cov_total.info
unittests: add local UT coverage Collect coverage info when running UT locally when lcov is available. Change-Id: I34a8b60056775a25cd4a3906d59c4a42e7cc845f Signed-off-by: paul luse <paul.e.luse@intel.com>
2017-05-08 20:57:23 +00:00
git clean -f "*.gcda"
autotest.sh: remove extra files generated by lcov. Change-Id: I7d65ce6b7926559d11cfe659820be76f202aede5 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/366349 Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2017-06-20 22:29:43 +00:00
rm -f cov_base.info cov_test.info OLD_STDOUT OLD_STDERR
build: add CONFIG_COVERAGE code coverage option Collect coverage information for use with gcov. Coverage is disabled on FreeBSD because the current version of clang provided by FreeBSD can't successfully link with -ftest-coverage enabled (the compiler-rt support libs are too old). Change-Id: Icc444936caa852bfb9a02b37223209319a27a770 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2015-10-22 18:26:21 +00:00
fi
Reference in New Issue Copy Permalink