Re: [bug report][regression] blktests nvme/029 failed on latest linux-block/for-next

[Nilay Shroff <nilay@linux.ibm.com>]

On 11/19/24 16:34, Yi Zhang wrote:
> Hello
> 
> CKI recently reported the blktests nvme/029 failed[1] on the
> linux-block/for-next, and bisect shows it was introduced from [2],
> please help check it and let me know if you need any info/test for it, thanks.
> 
> [1]
> nvme/029 (tr=loop) (test userspace IO via nvme-cli read/write
> interface) [failed]
>     runtime    ...  1.568s
>     --- tests/nvme/029.out 2024-11-19 08:13:41.379272231 +0000
>     +++ /root/blktests/results/nodev_tr_loop/nvme/029.out.bad
> 2024-11-19 10:55:13.615939542 +0000
>     @@ -1,2 +1,8 @@
>      Running nvme/029
>     +FAIL
>     +FAIL
>     +FAIL
>     +FAIL
>     +FAIL
>     +FAIL
>     ...
>     (Run 'diff -u tests/nvme/029.out
> /root/blktests/results/nodev_tr_loop/nvme/029.out.bad' to see the
> entire diff)
> [2]
> 64a51080eaba (HEAD) nvmet: implement id ns for nvm command set
> 
> 
> --
> Best Regards,
>   Yi Zhang
> 
> 
I couldn't reproduce it even after running nvme/029 in a loop 
for multiple times. Are you following any specific steps to 
recreate it?

Thanks,
--Nilay