Skip to content

README.md: Require nvme-cli >= 3.0 - #263

Open
Mr-Bossman wants to merge 1 commit into
linux-blktests:masterfrom
Mr-Bossman:dev/jesse/readme
Open

README.md: Require nvme-cli >= 3.0#263
Mr-Bossman wants to merge 1 commit into
linux-blktests:masterfrom
Mr-Bossman:dev/jesse/readme

Conversation

@Mr-Bossman

Copy link
Copy Markdown
Contributor

Commit df7cf50 ("nvme: rely on nvme-cli status code") changed nvme-cli to use the exit code to determine the result of the command, which is only available in nvme-cli >= 3.0. This commit updates the readme to match this requirement.

Commit df7cf50 ("nvme: rely on nvme-cli status code")
changed nvme-cli to use the exit code to determine the result
of the command, which is only available in nvme-cli >= 3.0.
This commit updates the readme to match this requirement.

Signed-off-by: Jesse Taube <jtaubepe@redhat.com>
@igaw

igaw commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

nvme-cli 2.16 also returns error codes, there is no hard dependency on 3.0.

@kawasaki

Copy link
Copy Markdown
Collaborator

Thanks for this PR, but I have the same view as @igaw . Quite a few blktests users will keep on running blktests with nvme-cli older than 3.0, and I do not want to upset them. For that purpose, blktests should work with the older nvme-cli. If you see any failure with older nvme-cli versions, report will be appreciated.

@Mr-Bossman

Copy link
Copy Markdown
Contributor Author

If you see any failure with older nvme-cli versions, report will be appreciated.

Yes let me see if i can make a simple example. The gist is that nvme disconnect for v2.16 sometimes returns 1 even if the disconnect was successful, it only happens sometimes though.

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.

3 participants