d/numam-spdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
a1591e23c4
numam-spdk/test/nvmf
History
Karol Latecki db43b387ba test: do not use iter_pci_class_code in tests 
Do not use iter_pci_class_code function in tests to
iterate over NVMe drives. This function can return
drives which at the moment of execution can not be
whitelisted for use.

This can result in test errors (such as simply
bdev_nvme_attach_controller RPC command failing) or
even using and deleting data from NVMe drive which
was not meant to be used in tests.

Fixes #1235

Change-Id: I82b9935fc88605b636c2096be6c71d4880a567c8
Signed-off-by: Karol Latecki <karol.latecki@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/1309
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>
2020-03-18 08:03:21 +00:00
..
host test: do not use iter_pci_class_code in tests 2020-03-18 08:03:21 +00:00
target test: do not use iter_pci_class_code in tests 2020-03-18 08:03:21 +00:00
common.sh test/common: Source *_APP from a common place 2020-02-27 10:15:40 +00:00
nvmf.sh test/nvmf: Add skel for nvmf error testing 2020-02-27 10:15:40 +00:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

README.md

NVMe-oF test scripts

The test scripts in this directory hierarchy can be run in isolation by passing the --iso flag when running the test script. This will set up the RDMA NIC for testing and then tear it back down again when the test is completed.