* blktests nvme/042 nvme/043 fail ?
@ 2024-05-26 10:17 Sagi Grimberg
2024-05-27 5:22 ` Daniel Wagner
2024-05-29 22:06 ` Chaitanya Kulkarni
0 siblings, 2 replies; 3+ messages in thread
From: Sagi Grimberg @ 2024-05-26 10:17 UTC (permalink / raw)
To: open list:NVM EXPRESS DRIVER, Hannes Reinecke, Daniel Wagner,
Shin'ichiro Kawasaki
Is anyone else seeing these errors?
--
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
WARNING: Test did not clean up port: 0
WARNING: Test did not clean up subsystem: blktests-subsystem-1
rmdir: failed to remove
'/sys/kernel/config/nvmet//subsystems/blktests-subsystem-1': Directory
not empty
WARNING: Test did not clean up host:
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
rmdir: failed to remove
'/sys/kernel/config/nvmet//hosts/nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349':
Devnvme/042 (tr=tcp) (Test dhchap key types for authenticated
connections) [failed]
runtime ... 0.316s
--- tests/nvme/042.out 2024-05-26 10:06:14.563557068 +0000
+++ /root/blktests/results/nodev_tr_tcp/nvme/042.out.bad 2024-05-26
10:13:42.430937572 +0000
@@ -2,15 +2,4 @@
Testing hmac 0
disconnected 1 controller(s)
Testing hmac 1
-disconnected 1 controller(s)
-Testing hmac 2
-disconnected 1 controller(s)
-Testing hmac 3
...
(Run 'diff -u tests/nvme/042.out
/root/blktests/results/nodev_tr_tcp/nvme/042.out.bad' to see the entire
diff)
WARNING: Test did not clean up subsystem: blktests-subsystem-1
rmdir: failed to remove
'/sys/kernel/config/nvmet//subsystems/blktests-subsystem-1': Directory
not empty
WARNING: Test did not clean up host:
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
rmdir: failed to remove
'/sys/kernel/config/nvmet//hosts/nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349':
Device or resource busy
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections)
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [failed]
runtime ... 130.513s
--- tests/nvme/043.out 2024-05-26 10:06:14.563557068 +0000
+++ /root/blktests/results/nodev_tr_tcp/nvme/043.out.bad 2024-05-26
10:15:53.258812323 +0000
@@ -1,18 +1,19 @@
Running nvme/043
+FAIL target setup failed. stale host configuration found
Testing hash hmac(sha256)
-disconnected 1 controller(s)
+disconnected 0 controller(s)
Testing hash hmac(sha384)
-disconnected 1 controller(s)
...
(Run 'diff -u tests/nvme/043.out
/root/blktests/results/nodev_tr_tcp/nvme/043.out.bad' to see the entire
diff)
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blktests nvme/042 nvme/043 fail ?
2024-05-26 10:17 blktests nvme/042 nvme/043 fail ? Sagi Grimberg
@ 2024-05-27 5:22 ` Daniel Wagner
2024-05-29 22:06 ` Chaitanya Kulkarni
1 sibling, 0 replies; 3+ messages in thread
From: Daniel Wagner @ 2024-05-27 5:22 UTC (permalink / raw)
To: Sagi Grimberg
Cc: open list:NVM EXPRESS DRIVER, Hannes Reinecke,
Shin'ichiro Kawasaki
On Sun, May 26, 2024 at 01:17:25PM GMT, Sagi Grimberg wrote:
> Is anyone else seeing these errors?
No, I haven't seen these yet. Which branch is this, nvme-6.10 or master?
I'll try to reproduce it.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blktests nvme/042 nvme/043 fail ?
2024-05-26 10:17 blktests nvme/042 nvme/043 fail ? Sagi Grimberg
2024-05-27 5:22 ` Daniel Wagner
@ 2024-05-29 22:06 ` Chaitanya Kulkarni
1 sibling, 0 replies; 3+ messages in thread
From: Chaitanya Kulkarni @ 2024-05-29 22:06 UTC (permalink / raw)
To: Sagi Grimberg
Cc: Hannes Reinecke, Daniel Wagner, Shin'ichiro Kawasaki,
open list:NVM EXPRESS DRIVER
On 5/26/24 03:17, Sagi Grimberg wrote:
> Is anyone else seeing these errors?
> --
> nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
> WARNING: Test did not clean up port: 0
> WARNING: Test did not clean up subsystem: blktests-subsystem-1
> rmdir: failed to remove
> '/sys/kernel/config/nvmet//subsystems/blktests-subsystem-1': Directory
> not empty
> WARNING: Test did not clean up host:
> nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
> rmdir: failed to remove
> '/sys/kernel/config/nvmet//hosts/nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349':
> Devnvme/042 (tr=tcp) (Test dhchap key types for authenticated
> connections) [failed]
> runtime ... 0.316s
> --- tests/nvme/042.out 2024-05-26 10:06:14.563557068 +0000
> +++ /root/blktests/results/nodev_tr_tcp/nvme/042.out.bad
> 2024-05-26 10:13:42.430937572 +0000
> @@ -2,15 +2,4 @@
> Testing hmac 0
> disconnected 1 controller(s)
> Testing hmac 1
> -disconnected 1 controller(s)
> -Testing hmac 2
> -disconnected 1 controller(s)
> -Testing hmac 3
> ...
> (Run 'diff -u tests/nvme/042.out
> /root/blktests/results/nodev_tr_tcp/nvme/042.out.bad' to see the
> entire diff)
> WARNING: Test did not clean up subsystem: blktests-subsystem-1
> rmdir: failed to remove
> '/sys/kernel/config/nvmet//subsystems/blktests-subsystem-1': Directory
> not empty
> WARNING: Test did not clean up host:
> nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
> rmdir: failed to remove
> '/sys/kernel/config/nvmet//hosts/nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349':
> Device or resource busy
> nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
> connections)
>
> nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
> connections) [failed]
> runtime ... 130.513s
> --- tests/nvme/043.out 2024-05-26 10:06:14.563557068 +0000
> +++ /root/blktests/results/nodev_tr_tcp/nvme/043.out.bad
> 2024-05-26 10:15:53.258812323 +0000
> @@ -1,18 +1,19 @@
> Running nvme/043
> +FAIL target setup failed. stale host configuration found
> Testing hash hmac(sha256)
> -disconnected 1 controller(s)
> +disconnected 0 controller(s)
> Testing hash hmac(sha384)
> -disconnected 1 controller(s)
> ...
> (Run 'diff -u tests/nvme/043.out
> /root/blktests/results/nodev_tr_tcp/nvme/043.out.bad' to see the
> entire diff)
> --
>
no I've not seen these failures, just finished running blktests on latest
nvme-6.10 branch and they are passing see below [1]. I've also tried
nvme/042 nvme/043 in a loop for 10 times, no failure [2].
-ck
[1]
blktests (master) # nvme_trtype=tcp ./check nvme
nvme/002 (tr=tcp) (create many subsystems and test discovery) [not run]
nvme_trtype=tcp is not supported in this test
nvme/003 (tr=tcp) (test if we're sending keep-alives to a discovery
controller) [passed]
runtime 11.243s ... 11.238s
nvme/004 (tr=tcp) (test nvme and nvmet UUID NS descriptors) [passed]
runtime 0.270s ... 0.246s
nvme/005 (tr=tcp) (reset local loopback target) [passed]
runtime 0.318s ... 0.311s
nvme/006 (tr=tcp bd=device) (create an NVMeOF target) [passed]
runtime 0.090s ... 0.087s
nvme/006 (tr=tcp bd=file) (create an NVMeOF target) [passed]
runtime 0.069s ... 0.074s
nvme/008 (tr=tcp bd=device) (create an NVMeOF host) [passed]
runtime 0.250s ... 0.245s
nvme/008 (tr=tcp bd=file) (create an NVMeOF host) [passed]
runtime 0.218s ... 0.206s
nvme/010 (tr=tcp bd=device) (run data verification fio job) [passed]
runtime 61.985s ... 64.322s
nvme/010 (tr=tcp bd=file) (run data verification fio job) [passed]
runtime 97.814s ... 97.964s
nvme/012 (tr=tcp bd=device) (run mkfs and data verification fio) [passed]
runtime 70.609s ... 68.434s
nvme/012 (tr=tcp bd=file) (run mkfs and data verification fio) [passed]
runtime 108.101s ... 103.278s
nvme/014 (tr=tcp bd=device) (flush a command from host) [passed]
runtime 8.673s ... 7.905s
nvme/014 (tr=tcp bd=file) (flush a command from host) [passed]
runtime 6.569s ... 6.517s
nvme/016 (tr=tcp) (create/delete many NVMeOF block device-backed ns and
test discovery) [not run]
nvme_trtype=tcp is not supported in this test
nvme/017 (tr=tcp) (create/delete many file-ns and test discovery) [not run]
nvme_trtype=tcp is not supported in this test
nvme/018 (tr=tcp) (unit test NVMe-oF out of range access on a file
backend) [passed]
runtime 0.223s ... 0.221s
nvme/019 (tr=tcp bd=device) (test NVMe DSM Discard command) [passed]
runtime 0.250s ... 0.255s
nvme/019 (tr=tcp bd=file) (test NVMe DSM Discard command) [passed]
runtime 0.236s ... 0.228s
nvme/021 (tr=tcp bd=device) (test NVMe list command) [passed]
runtime 0.247s ... 0.232s
nvme/021 (tr=tcp bd=file) (test NVMe list command) [passed]
runtime 0.209s ... 0.221s
nvme/022 (tr=tcp bd=device) (test NVMe reset command) [passed]
runtime 0.338s ... 0.308s
nvme/022 (tr=tcp bd=file) (test NVMe reset command) [passed]
runtime 0.303s ... 0.283s
nvme/023 (tr=tcp bd=device) (test NVMe smart-log command) [passed]
runtime 0.243s ... 0.232s
nvme/023 (tr=tcp bd=file) (test NVMe smart-log command) [passed]
runtime 0.234s ... 0.208s
nvme/025 (tr=tcp bd=device) (test NVMe effects-log) [passed]
runtime 0.240s ... 0.229s
nvme/025 (tr=tcp bd=file) (test NVMe effects-log) [passed]
runtime 0.209s ... 0.217s
nvme/026 (tr=tcp bd=device) (test NVMe ns-descs) [passed]
runtime 0.253s ... 0.258s
nvme/026 (tr=tcp bd=file) (test NVMe ns-descs) [passed]
runtime 0.219s ... 0.238s
nvme/027 (tr=tcp bd=device) (test NVMe ns-rescan command) [passed]
runtime 0.261s ... 0.284s
nvme/027 (tr=tcp bd=file) (test NVMe ns-rescan command) [passed]
runtime 0.272s ... 0.256s
nvme/028 (tr=tcp bd=device) (test NVMe list-subsys) [passed]
runtime 0.247s ... 0.247s
nvme/028 (tr=tcp bd=file) (test NVMe list-subsys) [passed]
runtime 0.220s ... 0.224s
nvme/029 (tr=tcp) (test userspace IO via nvme-cli read/write interface)
[passed]
runtime 0.437s ... 0.429s
nvme/030 (tr=tcp) (ensure the discovery generation counter is updated
appropriately) [passed]
runtime 0.171s ... 0.171s
nvme/031 (tr=tcp) (test deletion of NVMeOF controllers immediately after
setup) [passed]
runtime 2.169s ... 2.120s
nvme/038 (tr=tcp) (test deletion of NVMeOF subsystem without enabling)
[passed]
runtime 0.022s ... 0.022s
nvme/040 (tr=tcp) (test nvme fabrics controller reset/disconnect
operation during I/O) [passed]
runtime 6.299s ... 6.259s
nvme/041 (tr=tcp) (Create authenticated connections) [passed]
runtime 1.728s ... 1.709s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.952s ... 3.974s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 24.013s ... 24.121s
nvme/044 (tr=tcp) (Test bi-directional authentication) [passed]
runtime 3.620s ... 3.577s
nvme/045 (tr=tcp) (Test re-authentication) [passed]
runtime 1.986s ... 2.014s
common/rc: line 213: 0vme: value too great for base (error token is "0vme")
nvme/048 (tr=tcp) (Test queue count changes on reconnect) [passed]
runtime 6.302s ... 5.300s
nvme/052 (tr=tcp) (test nvmet concurrent ns enable/disable) [passed]
runtime 2.194s ... 2.206s
[2]
blktests (master) # for ((j=0;j<10;j++)); do for i in 042 043; do
nvme_trtype=tcp ./check nvme/$i; done; done
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.951s ... 3.972s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime ... 19.543s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.972s ... 3.849s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.543s ... 19.605s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.849s ... 3.991s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.605s ... 19.596s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.991s ... 4.012s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.596s ... 19.412s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 4.012s ... 3.957s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.412s ... 19.679s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.957s ... 3.965s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.679s ... 19.599s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.965s ... 3.974s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.599s ... 19.677s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.974s ... 3.984s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.677s ... 19.655s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.984s ... 3.997s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.655s ... 19.513s
nvme/042 (tr=tcp) (Test dhchap key types for authenticated connections)
[passed]
runtime 3.997s ... 3.936s
nvme/043 (tr=tcp) (Test hash and DH group variations for authenticated
connections) [passed]
runtime 19.513s ... 19.664s
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-05-29 22:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-05-26 10:17 blktests nvme/042 nvme/043 fail ? Sagi Grimberg
2024-05-27 5:22 ` Daniel Wagner
2024-05-29 22:06 ` Chaitanya Kulkarni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox