[PATCH blktests 2/2] nvme/060: suppress "nvme connect" failure for rdma transport

[Shin'ichiro Kawasaki]

The test case nvme/060 often fails for the rdma transport with the
message "FAIL: nvme connect return error code":

nvme/060 (tr=rdma) (test nvme fabrics target reset)          [failed]
    runtime  86.258s  ...  23.604s
    --- tests/nvme/060.out	2025-08-26 21:28:52.798847739 +0900
    +++ /home/shin/Blktests/blktests/results/nodev_tr_rdma/nvme/060.out.bad	2026-06-18 15:36:18.239424796 +0900
    @@ -1,2 +1,3 @@
     Running nvme/060
    +FAIL: nvme connect return error code
     Test complete

The test case repeats nvme connect and disconnect while controller
resets are repeated in parallel. In this situation, connect failures are
expected and should not alarm users. Suppress the failure message for
the rdma transport.

Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki at wdc.com>
---
 tests/nvme/060 | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/tests/nvme/060 b/tests/nvme/060
index 9e694af..49786af 100755
--- a/tests/nvme/060
+++ b/tests/nvme/060
@@ -19,6 +19,12 @@ set_conditions() {
 	_set_nvme_trtype "$@"
 }
 
+filter_connect_msg() {
+	if [[ ${nvme_trtype} == rdma ]]; then
+		grep --invert-match "nvme connect return error code"
+	fi
+}
+
 filter_state_write_msg() {
 	grep --invert-match "state: No such file or directory"
 }
@@ -56,7 +62,8 @@ test() {
 	# The target reset is triggered with an even number timeout, while the
 	# host reconnects with an odd number timeout.
 	for ((i = 0; i <= 5; i++)); do
-		_nvme_connect_subsys --keep-alive-tmo 1 --reconnect-delay 1 --no-wait-ns
+		_nvme_connect_subsys --keep-alive-tmo 1 --reconnect-delay 1 \
+				     --no-wait-ns | filter_connect_msg
 		sleep 3
 		_nvme_disconnect_subsys >> "$FULL" 2>&1
 	done
-- 
2.54.0