On Fri, Jun 6, 2025 at 3:55 PM Shinichiro Kawasaki <shinichiro.kawasaki@xxxxxxx> wrote: > > To+: Yi, > > On Jun 05, 2025 / 15:02, Daniel Wagner wrote: > > Hi, > > Hi Daniel, thank you for the fix actions! > > > > > On Thu, May 29, 2025 at 08:46:35AM +0000, Shinichiro Kawasaki wrote: > > > #1: nvme/023 > > > > > > When libnvme has version 1.13 or later and built with liburing, nvme-cli > > > command "nvme smart-log" command fails for namespace block devices. This > > > makes the test case nvme/032 fail [2]. Fix in libnvme is expected. > > > > > > [2] > > > https://lore.kernel.org/linux-nvme/32c3e9ef-ab3c-40b5-989a-7aa323f5d611@flourine.local/T/#m6519ce3e641e7011231d955d9002d1078510e3ee > > > > Should be fixed now. If you want, I can do another release soon, so the > > fix get packaged up by the distros. > > As of today, CKI project keeps on reporting the failure: > > https://datawarehouse.cki-project.org/kcidb/tests/redhat:1851238698-aarch64-kernel_upt_7 > > Yi, do you think the new libnvme release will help to silence the failure I've created one CKI issue to track the nvme/023 failure, so the failure will be waived in the future test. > reports? I'm guessing the release will help RedHat to pick up and apply to CKI Yes, if we have the new release for libnvme, our Fedora libnvme maintainer can build the new one for Fedora. I also created the Fedora issue to track it on libnvme side. https://bugzilla.redhat.com/show_bug.cgi?id=2370805 > blktests runs. > -- Best Regards, Yi Zhang
