-
Notifications
You must be signed in to change notification settings - Fork 699
Nvme tests ns #2673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nvme tests ns #2673
Conversation
Since currently only default NS blkdev checked for all NSs. Signed-off-by: Tokunori Ikegami <[email protected]>
|
The changes related to the issue #2668 but still the issue cause not sure and the blkdev checking fix may detect the cause. Also add verbose debugging option for NS management commands. |
tests/nvme_test.py
Outdated
| err = subprocess.call(id_ns_cmd, | ||
| shell=True, | ||
| stdout=subprocess.DEVNULL) | ||
| if err == 0: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suppose this should be indented, only test the return value from the subprocess.call?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed the indentation. Thank you.
tests/nvme_test.py
Outdated
| create_ns_cmd = f"{self.nvme_bin} create-ns {self.ctrl} " + \ | ||
| f"--nsze={str(nsze)} --ncap={str(ncap)} --flbas={str(flbas)} " + \ | ||
| f"--dps={str(dps)}" | ||
| f"--dps={str(dps)} -v" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if we want the spam the output. Usually this stuff works just fine. I let @MaisenbacherD decide :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Understood. Thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with enabling verbosity output for tests, as this might give hints why a test failed when skimming though the logs.
However, can we please use the long version of the options for scripting (e.g. --verbose)? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right so fixed to the long version option. Thank you.
To make sure the blkdev as same with NS attachment. Signed-off-by: Tokunori Ikegami <[email protected]>
d463a3d to
9ea6705
Compare
This is for debugging output if test failed. Signed-off-by: Tokunori Ikegami <[email protected]>
9ea6705 to
388bc3f
Compare
MaisenbacherD
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me :)
|
Thanks! |
No description provided.