ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
77d591e172
Spdk/test/nvmf/target/filesystem.sh

85 lines
2.3 KiB
Bash
Raw Normal View History

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
#!/usr/bin/env bash
testdir=$(readlink -f $(dirname $0))
nvmf: evaluate .. in $rootdir Make the path to the executable shorter so it fits in the coredump. Change-Id: I651c6cb4bd37fea51dd8e39b47a97c4edeace22f Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-06 16:56:03 +00:00
rootdir=$(readlink -f $testdir/../../..)
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
nvmf: create a common script file for nvmf automation test Put the common funcs in test/nvmf/common.sh to reduce duplicated code Change-Id: I1c72f6fb22d092dafb7fb134b8bb3780b5525e48 Signed-off-by: Ziye Yang <ziye.yang@intel.com> Signed-off-by: Gang Cao <gang.cao@intel.com>
2016-06-08 01:47:02 +00:00
source $rootdir/test/nvmf/common.sh
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
test: Create malloc bdev dynamically for nvmf test cases. Change-Id: I64ec6eb16ff8480ce95fbd2c07d479c4d05965e9 Signed-off-by: Cunyin Chang <cunyin.chang@intel.com>
2016-10-17 09:38:26 +00:00
MALLOC_BDEV_SIZE=64
MALLOC_BLOCK_SIZE=512
scripts: use python3 in all scripts This it to prepare for RPM package. Also lower number of dependencies needed by SPDK tools. Update changelog to deprecate Python 2 and explicit interpeter invoking in scripts. Change-Id: I2497cca721cbcbadc1c99c675f8b8b7f682d5efa Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Reviewed-on: https://review.gerrithub.io/425233 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2018-09-11 13:26:14 +00:00
rpc_py="$rootdir/scripts/rpc.py"
test: Use rpc methods to create nvmf subsystem. Change-Id: I5db50a2db0b7096a10fb97406d51410c1678dc92 Signed-off-by: Cunyin Chang <cunyin.chang@intel.com>
2016-09-27 00:38:36 +00:00
test/nvmf: simplify "iso" parameter Pull this parameter when sourcing common.sh and set a RUN_IN_ISOLATION flag if it was specified. This reduces the overall code a bit plus avoids having to pass the "iso" parameter to nvmftestinit and nvmftestfini. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Idbbe27bfb7b62857500176cdb5d90e381fce4ffc Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454814 Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-16 19:38:53 +00:00
nvmftestinit
test/nvmf: add init and fini functions to tgt tests These functions enable a user to run one of the Nvme-oF tests directly from the command line without having to manually invoke all of the setup we typically do. Change-Id: Ib0baa77c08abb24c2fa2a1e21cf38ac613d663e0 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/422336 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> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
2018-08-14 18:05:15 +00:00
test/nvmf: convert filesystem to use run_test This test specifically gets a little more complicated looking when we do the test this way, but the goal is to enable deterministic reporting of test completions on a per build basis. Change-Id: Ica36986f821337c22654fb4cc25f9a72a3d73517 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476825 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 00:23:48 +00:00
function nvmf_filesystem_create {
fstype=$1
if [ $fstype = ext4 ]; then
force=-F
else
force=-f
fi
mkfs.${fstype} $force /dev/nvme0n1p1
mount /dev/nvme0n1p1 /mnt/device
touch /mnt/device/aaa
sync
rm /mnt/device/aaa
sync
umount /mnt/device
}
function nvmf_filesystem_part {
incapsule=$1
test/nvmf: reduce duplication between target scripts All of the checking for NVMF_FIRST_TARGET_IP, starting the target, waiting on the target and modprobing nvme-rdma is duplicated in every script. So move a lot of this either to nvmftestinit() or a new nvmfappstart() function in common.sh. Also just kill the nvmf target in nvmftestfini, rather than the script to explicitly kill it. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I5864404610a4244473f460d48264de92687ed867 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454678 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-13 19:11:00 +00:00
nvmfappstart "-m 0xF"
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
test/nvmf: add NVMF_TRANSPORT_OPTS global For a lot of the tests, we may want to specify different options for each transport. I believe this will be more prevalent as we add more transport specific options. Change-Id: I83a915629460d1d869eaba4bc86822d7563402ac Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/461740 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
2019-07-15 04:42:41 +00:00
$rpc_py nvmf_create_transport $NVMF_TRANSPORT_OPTS -u 8192 -c $incapsule
scripts/rpc: Change rpc construct_malloc_bdev to bdev_malloc_create This is patch that implements changes according to proposal submitted in https://review.gerrithub.io/c/spdk/spdk/+/453036 Change-Id: I5423cd34cb5fc111b34cab2b7f7c6c5f11898af8 Signed-off-by: Pawel Kaminski <pawelx.kaminski@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/464677 Reviewed-by: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-08-09 11:15:35 +00:00
$rpc_py bdev_malloc_create $MALLOC_BDEV_SIZE $MALLOC_BLOCK_SIZE -b Malloc1
RPC: rename nvmf_subsystem_create to nvmf_create_subsystem Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Ic3aa9f168b2e612e461c450ef1e5e1ae81fa5635 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468963 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-09-20 10:22:44 +00:00
$rpc_py nvmf_create_subsystem nqn.2016-06.io.spdk:cnode1 -a -s SPDK00000000000001
test/nvmf: run filesystem.sh against just 1 malloc bdev Adding the second bdev doesn't provide any real value since it's the same kind of bdev. While here, explicitly name the malloc bdev to simplify the test some more. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ide6da901d4b90383cc73fa195b5a070a8eda0d01 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454687 Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Paul Luse <paul.e.luse@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-15 23:10:30 +00:00
$rpc_py nvmf_subsystem_add_ns nqn.2016-06.io.spdk:cnode1 Malloc1
test/nvmf: use TEST_TRANSPORT instead of 'rdma' This prepares for using scripts for tcp testing as well. Note that this patch just hardcoded TEST_TRANSPORT to 'rdma' for now. An upcoming patch will require the caller to pass --transport=rdma instead. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I085fdf51910aaf960959c71c73a187be41fd7ee8 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456667 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-06-03 16:34:31 +00:00
$rpc_py nvmf_subsystem_add_listener nqn.2016-06.io.spdk:cnode1 -t $TEST_TRANSPORT -a $NVMF_FIRST_TARGET_IP -s $NVMF_PORT
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
test/nvmf: use TEST_TRANSPORT instead of 'rdma' This prepares for using scripts for tcp testing as well. Note that this patch just hardcoded TEST_TRANSPORT to 'rdma' for now. An upcoming patch will require the caller to pass --transport=rdma instead. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I085fdf51910aaf960959c71c73a187be41fd7ee8 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456667 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-06-03 16:34:31 +00:00
nvme connect -t $TEST_TRANSPORT -n "nqn.2016-06.io.spdk:cnode1" -a "$NVMF_FIRST_TARGET_IP" -s "$NVMF_PORT"
test/nvmf: confirm kernel finds NVMe-oF namespaces In Fedora 27 the nvme program returns before the kernel has loaded the namespces associated with the subsystem. This patch ensures that those namespaces can be enumerated by the kernel before we run any tests on them. Change-Id: I77505ed5cd5b1118a841650851fa5ecaf76f5619 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/407829 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
2018-04-16 20:28:16 +00:00
test/nvmf/filesystem: explicitly use nvme0n1 This test has always relied on /dev/nvme0n1 being the location of our test drive which means that it is the only one in the system at the time the test is run. So instead of trying to loop multiple non-existant nvme drives, just call it out directly. Also, add a todo to remove the dependence on NVMe0n1 since we could run this test on a machine where the main filesystem is on an NVMe drive which would break this test. Change-Id: Ibb2448d9367a5c80d85a1c91b0c6e44e58237751 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476952 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 21:05:18 +00:00
# TODO: fix this to wait for the proper NVMe device.
# if we are hosting the local filesystem on an NVMe drive, this test will fail
# because it relies on the no other NVMe drives being present in the system.
test/nvmf: test InCapsuleDataSize 0 in filesystem.sh Change-Id: I939aef31473b6a7acae879fb5b03a62154390cac Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418729 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>
2018-07-09 18:11:00 +00:00
waitforblk "nvme0n1"
test/nvmf: clean up filesystem test Inline function that is only called once. Fix == bashism. Create the filesystems on the partition created by parted rather than on the raw namespace block device. Add 'sync' invocations to make sure data gets flushed to the block device we are testing. Drop the copy-pasted FIO cleanup code (filesystem test does not run FIO). Change-Id: Id47d68db208a618841291c4184824031476268f1 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-08 22:43:07 +00:00
test/nvmf: test InCapsuleDataSize 0 in filesystem.sh Change-Id: I939aef31473b6a7acae879fb5b03a62154390cac Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418729 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>
2018-07-09 18:11:00 +00:00
mkdir -p /mnt/device
test/nvmf: clean up filesystem test Inline function that is only called once. Fix == bashism. Create the filesystems on the partition created by parted rather than on the raw namespace block device. Add 'sync' invocations to make sure data gets flushed to the block device we are testing. Drop the copy-pasted FIO cleanup code (filesystem test does not run FIO). Change-Id: Id47d68db208a618841291c4184824031476268f1 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
2016-07-08 22:43:07 +00:00
test/nvmf/filesystem: explicitly use nvme0n1 This test has always relied on /dev/nvme0n1 being the location of our test drive which means that it is the only one in the system at the time the test is run. So instead of trying to loop multiple non-existant nvme drives, just call it out directly. Also, add a todo to remove the dependence on NVMe0n1 since we could run this test on a machine where the main filesystem is on an NVMe drive which would break this test. Change-Id: Ibb2448d9367a5c80d85a1c91b0c6e44e58237751 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476952 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 21:05:18 +00:00
parted -s /dev/nvme0n1 mklabel msdos mkpart primary '0%' '100%'
partprobe
sleep 1
test/nvmf: convert filesystem to use run_test This test specifically gets a little more complicated looking when we do the test this way, but the goal is to enable deterministic reporting of test completions on a per build basis. Change-Id: Ica36986f821337c22654fb4cc25f9a72a3d73517 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476825 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 00:23:48 +00:00
if [ $incapsule -eq 0 ]; then
run_test "case" "filesystem_ext4" nvmf_filesystem_create "ext4"
run_test "case" "filesystem_btrfs" nvmf_filesystem_create "btrfs"
run_test "case" "filesystem_xfs" nvmf_filesystem_create "xfs"
else
run_test "case" "filesystem_incapsule_ext4" nvmf_filesystem_create "ext4"
run_test "case" "filesystem_incapsule_btrfs" nvmf_filesystem_create "btrfs"
run_test "case" "filesystem_incapsule_xfs" nvmf_filesystem_create "xfs"
fi
nvmf: Delete partitions when tests end Change-Id: Ia30e037e98df8b0c781ce769453bbf891091334d Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-07-21 22:54:23 +00:00
test/nvmf/filesystem: explicitly use nvme0n1 This test has always relied on /dev/nvme0n1 being the location of our test drive which means that it is the only one in the system at the time the test is run. So instead of trying to loop multiple non-existant nvme drives, just call it out directly. Also, add a todo to remove the dependence on NVMe0n1 since we could run this test on a machine where the main filesystem is on an NVMe drive which would break this test. Change-Id: Ibb2448d9367a5c80d85a1c91b0c6e44e58237751 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476952 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 21:05:18 +00:00
parted -s /dev/nvme0n1 rm 1
test/nvmf: test InCapsuleDataSize 0 in filesystem.sh Change-Id: I939aef31473b6a7acae879fb5b03a62154390cac Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418729 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>
2018-07-09 18:11:00 +00:00
sync
nvme disconnect -n "nqn.2016-06.io.spdk:cnode1" || true
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
RPC: rename delete_nvmf_subsystem to nvmf_delete_subsystem Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: I4654f254cae78b0def789b13754af7c70c73dabb Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/469111 Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-09-23 10:17:30 +00:00
$rpc_py nvmf_delete_subsystem nqn.2016-06.io.spdk:cnode1
nvmf: Disconnect the initiator on test exit. Change-Id: I8e640a77dc4c17582ff5ec0a4daba4f1d509c30c Signed-off-by: Ben Walker <benjamin.walker@intel.com>
2016-07-25 15:20:11 +00:00
test/nvmf: test InCapsuleDataSize 0 in filesystem.sh Change-Id: I939aef31473b6a7acae879fb5b03a62154390cac Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418729 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>
2018-07-09 18:11:00 +00:00
trap - SIGINT SIGTERM EXIT
killprocess $nvmfpid
test: properly handle the killprocess case To check whether the process already killed and if the process is not there, return error. This is to fix the below issue: https://github.com/spdk/spdk/issues/1066 Change-Id: I5f36213237a4b0eed8edbc69e666037cf17488b2 Signed-off-by: GangCao <gang.cao@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476127 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: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
2019-11-29 21:18:36 +00:00
nvmfpid=
test/nvmf: convert filesystem to use run_test This test specifically gets a little more complicated looking when we do the test this way, but the goal is to enable deterministic reporting of test completions on a per build basis. Change-Id: Ica36986f821337c22654fb4cc25f9a72a3d73517 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476825 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
2019-12-05 00:23:48 +00:00
}
run_test "suite" "nvmf_filesystem_no_incapsule" nvmf_filesystem_part 0
run_test "suite" "nvmf_filesystem_incapsule" nvmf_filesystem_part 4096
test: Use rpc methods to create nvmf subsystem. Change-Id: I5db50a2db0b7096a10fb97406d51410c1678dc92 Signed-off-by: Cunyin Chang <cunyin.chang@intel.com>
2016-09-27 00:38:36 +00:00
test/nvmf: simplify "iso" parameter Pull this parameter when sourcing common.sh and set a RUN_IN_ISOLATION flag if it was specified. This reduces the overall code a bit plus avoids having to pass the "iso" parameter to nvmftestinit and nvmftestfini. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Idbbe27bfb7b62857500176cdb5d90e381fce4ffc Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/454814 Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2019-05-16 19:38:53 +00:00
nvmftestfini
Reference in New Issue Copy Permalink