On Mar 18, 2025 / 11:39, Daniel Wagner wrote:
> Add a new test case which forcefully removes the target and setup it
> again.
This test case has a few shellcheck warnings.
tests/nvme/061:63:3: warning: connect_args appears unused. Verify use (or export if used externally). [SC2034]
tests/nvme/061:84:22: note: Double quote to prevent globbing and word splitting. [SC2086]
tests/nvme/061:89:22: note: Double quote to prevent globbing and word splitting. [SC2086]
When I ran the test case on my test system, I observed it failed. Is it
expected?
$ sudo ./check nvme/061
nvme/061 (tr=loop) (test teardown and setup fabrics target during I/O) [failed]
runtime 8.567s ... 8.896s
--- tests/nvme/061.out 2025-04-03 18:21:40.829107999 +0900
+++ /home/shin/Blktests/blktests/results/nodev_tr_loop/nvme/061.out.bad 2025-04-04 17:17:45.246929857 +0900
@@ -1,21 +1,9 @@
Running nvme/061
iteration 0
-state: connecting
-state: live
-iteration 1
-state: connecting
-state: live
...
(Run 'diff -u tests/nvme/061.out /home/shin/Blktests/blktests/results/nodev_tr_loop/nvme/061.out.bad' to see the entire diff)
$ cat results/nodev_tr_loop/nvme/061.out.bad
Running nvme/061
iteration 0
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
grep: /sys/class/nvme-fabrics/ctl//state: No such file or directory
expected state "connecting" not reached within 5 seconds
