tests: Temporarily skip some nvme tests on latest Fedora #1101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nvme_get_sanitize_log and nvme_get_self_test_log now return some invalid data for our test loop based NVMe devices. We'll skip the tests until this is resolved.
tbzatek
approved these changes
Apr 3, 2025
Member
tbzatek
left a comment
tbzatek
left a comment
There was a problem hiding this comment.
Hmm, just don't forget to revert this once we have proper libnvme fix!
Member
Author
|
Closing, the fix will be released soon in Fedora and it doesn't make sense to merge this for just few days and then revert it again. |
Member
Author
|
Seems to fix only half of the problem. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
nvme_get_sanitize_log and nvme_get_self_test_log now return some invalid data for our test loop based NVMe devices. We'll skip the tests until this is resolved.
See also #1098 and linux-nvme/libnvme#980