Skip to content

Conversation

@igaw
Copy link
Contributor

@igaw igaw commented Nov 26, 2025

Increase test coverage by checking if nvme connect is also reporting the expected return code.

At least nvme/031 seems to trigger sometimes FAILs.

To my surprise, nvme/041 for FC is passing with https://lore.kernel.org/linux-nvme/[email protected]/ applied. Nice :)

igaw added 2 commits November 26, 2025 09:00
There is no need to for the final / in the path. All users do add
another / when concatenation a path. This makes the path look more
consistent when debugging.

Signed-off-by: Daniel Wagner <[email protected]>
Don't ignore the nvme connect return codes. This ensures that all
transport behave the same.

Signed-off-by: Daniel Wagner <[email protected]>
@kawasaki
Copy link
Collaborator

kawasaki commented Jan 4, 2026

@igaw Thanks for this PR. This is great. I checked the two commits, and found two points below:

The first patch caused failure of the test case nvme/051, due to a missing "/". I added the "/".
The second patch has some improper indent. I fixed them.

With these changes, I applied the patches. Thanks!

@kawasaki kawasaki closed this Jan 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants