[draft]add new case for NVMe namespace management
Generally I would prefer if we would start using the JSON output instead the STDOUT of nvme-cli. The JSON output is there for machine parsing.
This would mean we add dependency on something like jq but IMO this would be better than continuing with the screen scraping.
Generally I would prefer if we would start using the JSON output instead the STDOUT of nvme-cli. The JSON output is there for machine parsing.
This would mean we add dependency on something like
jqbut IMO this would be better than continuing with the screen scraping.
Thanks, just update to get the value from json ouput.
Thanks for the patch. I have two comments:
-
I wanted to confirm the motivation to add this test case . Does it aim to test the kernel code? Or nvme devices? If it aim to cover kernel code, which part of the kernel code, or which feature of the kernel to cover? (Namespace detection feature?)
-
Can we ensure that the test target device status does not change before and after the test case run? For example, I wonder what will happen when multiple namespaces belong to a single controller, and one of the namespaces is the test target device.