On 2020-01-27 7:53 a.m., 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@xxxxxxx>
> ---
> tests/nvme/018 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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"
That's an odd message for an error... Error! I succeeded!
> nvme disconnect -n "${subsys_name}"
>
