qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 09/14] iotests: remove remaining calls to qemu_img_pipe()


From: Hanna Reitz
Subject: Re: [PATCH 09/14] iotests: remove remaining calls to qemu_img_pipe()
Date: Thu, 17 Mar 2022 13:43:50 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0

On 09.03.22 04:54, John Snow wrote:
As part of moving all python iotest invocations of qemu-img onto a
single qemu_img() implementation, remove a few lingering uses of
qemu_img_pipe() from outside of iotests.py itself.

Several cases here rely on the knowledge that qemu_img_pipe() suppresses
*all* output on a successful case when the command being issued is
'create'.

065: This call's output is inspected, but it appears as if it's expected
      to succeed. Replace this call with the checked qemu_img() variant
      instead to get better diagnostics if/when qemu-img itself fails.

237: "create" call output isn't actually logged. Use qemu_img_create()
      instead, which checks the return code. Remove the empty lines from
      the test output.

296: Two calls;
      -create: Expected to succeed. Like other create calls, the output
               isn't actually logged.  Switch to a checked variant
               (qemu_img_create) instead. The output for this test is
               a mixture of both test styles, so actually replace the
               blank line for readability.
      -amend:  This is expected to fail. Log the output.

After this patch, the only uses of qemu_img_pipe are internal to
iotests.py and will be removed in subsequent patches.

Signed-off-by: John Snow <jsnow@redhat.com>
---
  tests/qemu-iotests/065     |  4 ++--
  tests/qemu-iotests/237     |  3 +--
  tests/qemu-iotests/237.out |  3 ---
  tests/qemu-iotests/296     | 12 ++++++------
  4 files changed, 9 insertions(+), 13 deletions(-)

Reviewed-by: Hanna Reitz <hreitz@redhat.com>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]