Spdk/test/nvmf
Michal Berger e1dc45b0fa test/bdevperf: Keep bdevperf output around
Potential bdevperf failure is hidden out from the user as it's
std{out,err} is redirected to a file which is purged upon exiting
from the test.

For the sake of debugging, print contents of the output file before
removing it.

Change-Id: Ifd0ff94aa1812ec518c60ada5a63342d7d5b80dd
Signed-off-by: Michal Berger <michalx.berger@intel.com>
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3917
Community-CI: Mellanox Build Bot
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: Jim Harris <james.r.harris@intel.com>
2020-08-26 09:46:50 +00:00
..
host test/bdevperf: Keep bdevperf output around 2020-08-26 09:46:50 +00:00
target test/nvmf: Unify the ports in common file. 2020-08-17 08:20:58 +00:00
common.sh test/nvmf: Always remove lingering soft rxe devices 2020-08-21 08:24:29 +00:00
nvmf.sh test/nvmf: add a test for attaching to controllers. 2020-08-21 08:25:14 +00:00
README.md test: add parse_common_script_args function 2019-05-22 23:43:51 +00:00

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.