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

61 lines
2.6 KiB
Bash
Raw Normal View History

test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
#!/usr/bin/env bash
testdir=$(readlink -f $(dirname $0))
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
test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
if [ ! $(uname -s) = Linux ]; then
exit 0
fi
source $rootdir/test/nvmf/common.sh
test/nvmf: Don't use the stub Change-Id: I8581919aee1b95cc367cbfca905e434e5bf5ac4b Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/435936 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2018-12-03 19:41:07 +00:00
trap "exit 1" SIGINT SIGTERM EXIT
test/nvmf: use stub application The stub application will ensure that each nvmf test does not need to reinitialized DPDK memory and NVMe devices. This drastically cuts down on the amount of time needed to run all of the nvmf tests. Change-Id: I6abad4e1298111884f18026e72e36f5d8b73c4b9 Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362810 Reviewed-by: Jim Harris <james.r.harris@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2017-05-27 00:13:55 +00:00
test: Shellcheck - correct rule: Assigning an array to a string Correct shellcheck rule SC2124: Assigning an array to a string! Assign as array, or use * instead of @ to concatenate. Signed-off-by: Maciej Wawryk <maciejx.wawryk@intel.com> Change-Id: Id74c55b7e1c41b6469e84ac388cf8a5bd8e562a6 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/473276 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: Ben Walker <benjamin.walker@intel.com>
2019-11-05 12:06:34 +00:00
TEST_ARGS=( "$@" )
test/nvmf: add ARGS to nvmf.sh Right now this is empty, but we'll add to it later as part of parameterizing this script for different transports. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Icf0f67ce4dd886031c37986b352129d3c556bd92 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456684 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 19:30:05 +00:00
nvmf_example: add an nvmf example use the nvmf lib to add an nvmf example which doesn't use the spdk app framework. It can show how to use the nvmf lib to build your own nvmf target. We encouage you to use the RPC cmds so this example will not supply the configuration file. You can read the README.md to get the steps how to build your nvmf target and test the IO status. Change-Id: I8d175934f7364d40fb44d36e85c31d8ea5063654 Signed-off-by: JinYu <jin.yu@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/468457 Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: GangCao <gang.cao@intel.com>
2019-08-26 09:21:54 +00:00
run_test suite "nvmf_example" test/nvmf/target/nvmf_example.sh "${TEST_ARGS[@]}"
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_filesystem" test/nvmf/target/filesystem.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_discovery" test/nvmf/target/discovery.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_connect_disconnect" test/nvmf/target/connect_disconnect.sh "${TEST_ARGS[@]}"
test: add SPDK_TEST_NVME_CLI autotest flag As requested in GitHub issue #361, we should have a way to control whether the SPDK-patched nvme-cli tests are executed. Also add a report_test_completion call for the NVMe-oF nvme-cli test so we can easily track whether it executed (the local PCIe nvme-cli test already had a completion). Change-Id: I70c26bcf2489ccfa563214a9723603aa705be7ab Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418866 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: John Meneghini <johnm@netapp.com> Reviewed-by: <ed.rodriguez@netapp.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2018-07-10 16:32:30 +00:00
if [ $SPDK_TEST_NVME_CLI -eq 1 ]; then
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_nvme_cli" test/nvmf/target/nvme_cli.sh "${TEST_ARGS[@]}"
test: add SPDK_TEST_NVME_CLI autotest flag As requested in GitHub issue #361, we should have a way to control whether the SPDK-patched nvme-cli tests are executed. Also add a report_test_completion call for the NVMe-oF nvme-cli test so we can easily track whether it executed (the local PCIe nvme-cli test already had a completion). Change-Id: I70c26bcf2489ccfa563214a9723603aa705be7ab Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/418866 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: John Meneghini <johnm@netapp.com> Reviewed-by: <ed.rodriguez@netapp.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2018-07-10 16:32:30 +00:00
fi
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_lvol" test/nvmf/target/nvmf_lvol.sh "${TEST_ARGS[@]}"
test/nvmf: disable overwhelm testing for now. This test is causing intermittent failures on the test pool. Change-Id: I6be745700ee34813d49800acf689dc35d6c88ef4 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/451998 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>
2019-04-25 00:10:10 +00:00
#TODO: disabled due to intermittent failures. Need to triage.
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
# run_test suite "nvmf_srq_overwhelm" test/nvmf/target/srq_overwhelm.sh $TEST_ARGS
run_test suite "nvmf_vhost" test/nvmf/target/nvmf_vhost.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_bdev_io_wait" test/nvmf/target/bdev_io_wait.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_create_transport." test/nvmf/target/create_transport.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_multitarget" test/nvmf/target/multitarget.sh "${TEST_ARGS[@]}"
test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
test/nvmf: move multiconnection out of NIGHTLY_FAILING This test is now working reliably after commit 392f3ef58913 ("test/nvmf: fix waitforblk usage in multiconnection"). Change-Id: I15c790b01df8c8204b6c389cf8d381e10ee54fc9 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/413857 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-06-05 22:39:16 +00:00
if [ $RUN_NIGHTLY -eq 1 ]; then
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_fuzz" test/nvmf/target/fuzz.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_multiconnection" test/nvmf/target/multiconnection.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_initiator_timeout" test/nvmf/target/initiator_timeout.sh "${TEST_ARGS[@]}"
test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
fi
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_nmic" test/nvmf/target/nmic.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_rpc" test/nvmf/target/rpc.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_fio" test/nvmf/target/fio.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_shutdown" test/nvmf/target/shutdown.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_bdevio" test/nvmf/target/bdevio.sh "${TEST_ARGS[@]}"
test/nvmf: fix a couple of bugs in nvmf.sh 1) nmic is a target test - move it out of the host section 2) don't reset trap until after all tests have run 3) while here, move all of the target-related test together, followed by the host tests Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I73b3c0a8ace0ad65311ab7bb29b6cb08188e3aba Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452933 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-05-02 23:51:48 +00:00
test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
timing_enter host
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_bdevperf" test/nvmf/host/bdevperf.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_identify" test/nvmf/host/identify.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_perf" test/nvmf/host/perf.sh "${TEST_ARGS[@]}"
test/nvmf: run host/perf.sh separately for each transport While here, remove NVMF_TCP_IP_ADDRESS since we already have NVMF_FIRST_TARGET_IP which serves the same purpose when testing the TCP transport. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I7cc4712cd9746377937e889127aa5a61566d8846 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456705 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-06-03 22:22:51 +00:00
test/nvmf: disable identify_kernel test This test has been causing intermittent failures for some time: nvme_rdma.c: 221:nvme_rdma_get_event: *ERROR*: Expected RDMA_CM_EVENT_ESTABLISHED but received RDMA_CM_EVENT_UNREACHABLE (7) from CM event channel (status = -110) Disable it until we find a reliable way to avoid this issue. Change-Id: Id8f767bfa26a6a14f94cf4f7ff69b3ac0f11d88d Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/410489 Reviewed-by: Changpeng Liu <changpeng.liu@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> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
2018-05-08 19:54:15 +00:00
# TODO: disabled due to intermittent failures (RDMA_CM_EVENT_UNREACHABLE/ETIMEDOUT)
test/nvmf: add ARGS to nvmf.sh Right now this is empty, but we'll add to it later as part of parameterizing this script for different transports. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Icf0f67ce4dd886031c37986b352129d3c556bd92 Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/456684 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 19:30:05 +00:00
#run_test test/nvmf/host/identify_kernel_nvmf.sh $TEST_ARGS
test: add a test_name param to run_test This will allow us to use timing_enter and timing_exit directly inside the run_test function. That function already lends itself well to nesting the way we do our timing. This patch series is aimed at combining the timing_*, run_test, and report_test_completions calls all into a single place. This will greatly reduce the number of lines of code in our bash scripts devoted to tracking timing, formatting, and test completion. It will also enable us to expand on the reporting of test completions. Further down the line, this will also allow us to unify test case documentation. Change-Id: I8e1f4bcea86b2c3b88cc6e42339c57dfce4d58f2 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476799 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
2019-12-04 19:39:14 +00:00
run_test suite "nvmf_aer" test/nvmf/host/aer.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_fio" test/nvmf/host/fio.sh "${TEST_ARGS[@]}"
run_test suite "nvmf_target_disconnect" test/nvmf/host/target_disconnect.sh "${TEST_ARGS[@]}"
test: add nvmf multi-path testing Change-Id: Iea0c8e8c2405d008e77f8bea1a3c30f2f873fa3d Signed-off-by: Liang Yan <liang.z.yan@intel.com> Reviewed-on: https://review.gerrithub.io/420134 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>
2018-07-23 06:53:41 +00:00
test/nvmf: move the nvmf test cases to the separate script. Change-Id: I14dcb4c37d19b9696e6ad1ee088b37e34efbf3ff Signed-off-by: cunyinch <cunyin.chang@intel.com> Reviewed-on: https://review.gerrithub.io/362809 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-05-27 00:05:26 +00:00
timing_exit host
test/nvmf: fix a couple of bugs in nvmf.sh 1) nmic is a target test - move it out of the host section 2) don't reset trap until after all tests have run 3) while here, move all of the target-related test together, followed by the host tests Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I73b3c0a8ace0ad65311ab7bb29b6cb08188e3aba Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/452933 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Seth Howell <seth.howell5141@gmail.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
2019-05-02 23:51:48 +00:00
trap - SIGINT SIGTERM EXIT
test/nvmf: configure all nics when running NVMF tests. Change-Id: Ia40f0817320ac7f12312299633a7c40136c2e806 Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/371219 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>
2017-07-25 19:02:08 +00:00
revert_soft_roce
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
report_test_completion "nvmf"
Reference in New Issue Copy Permalink