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
..
aer.sh	test: add timing calls to run_test	2019-12-10 17:12:03 +00:00
bdevperf.sh	test/nvmf: disable bdevperf tests on soft-roce	2020-01-30 16:52:10 +00:00
fio.sh	test: do not use iter_pci_class_code in tests	2020-03-18 08:03:21 +00:00
identify_kernel_nvmf.sh	test: add timing calls to run_test	2019-12-10 17:12:03 +00:00
identify.sh	test/common: Source *_APP from a common place	2020-02-27 10:15:40 +00:00
perf.sh	test/nvmf: Add more cases in perf testing.	2020-03-16 08:45:36 +00:00
target_disconnect.sh	test/nvmf: don't return before calling nvmftestfini	2020-02-28 08:55:07 +00:00