Message ID | 20200129154619.103332-2-dwagner@suse.de (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | nmve/018 fixes | expand |
On 01/29/2020 07:46 AM, Daniel Wagner wrote: > nvme-cli writes 'CAP_EXCEEDED' message also on stdout not just > stderr. This lets the test fail as well. > > Fixes: 1aee5f430b30 ("nvme/018: Ignore error message generated by nvme read") > Signed-off-by: Daniel Wagner<dwagner@suse.de> > Reviewed-by: Logan Gunthorpe<logang@deltatee.com> Reviewed-by: Chaitanya Kulkarni@wdc.com
diff --git a/tests/nvme/018 b/tests/nvme/018 index 0a5b4c2ab019..d0f15db23538 100755 --- a/tests/nvme/018 +++ b/tests/nvme/018 @@ -43,7 +43,7 @@ test() { sectors="$(blockdev --getsz "/dev/${nvmedev}n1")" bs="$(blockdev --getbsz "/dev/${nvmedev}n1")" - nvme read "/dev/${nvmedev}n1" -s "$sectors" -c 0 -z "$bs" 2>"$FULL" \ + nvme read "/dev/${nvmedev}n1" -s "$sectors" -c 0 -z "$bs" &>"$FULL" \ && echo "ERROR: Successfully read out of device lba range" nvme disconnect -n "${subsys_name}"