qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
	vsementsov@virtuozzo.com, den@openvz.org, eblake@redhat.com,
	jsnow@redhat.com
Subject: [PATCH v5 01/12] iotests/277: use dot slash for nbd-fault-injector.py running
Date: Thu, 22 Oct 2020 21:56:16 +0300	[thread overview]
Message-ID: <20201022185627.16987-2-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20201022185627.16987-1-vsementsov@virtuozzo.com>

If you run './check 277', check includes common.config which adjusts
$PATH to include '.' first, and therefore finds nbd-fault-injector.py
on PATH.  But if you run './277' directly, there is nothing to adjust
PATH, and if '.' is not already on your PATH by other means, the test
fails because the executable is not found.  Adjust how we invoke the
helper executable to avoid needing a PATH search in the first place.

Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
---
 tests/qemu-iotests/277 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/qemu-iotests/277 b/tests/qemu-iotests/277
index d34f87021f..a39ce2d873 100755
--- a/tests/qemu-iotests/277
+++ b/tests/qemu-iotests/277
@@ -42,7 +42,7 @@ def make_conf_file(event):
 def start_server_NBD(event):
     make_conf_file(event)
 
-    srv = subprocess.Popen(['nbd-fault-injector.py', '--classic-negotiation',
+    srv = subprocess.Popen(['./nbd-fault-injector.py', '--classic-negotiation',
                            nbd_sock, conf_file], stdout=subprocess.PIPE,
                            stderr=subprocess.STDOUT, universal_newlines=True)
     line = srv.stdout.readline()
-- 
2.21.3



  reply	other threads:[~2020-10-22 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 18:56 [PATCH v5 00/12] Rework iotests/check Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` Vladimir Sementsov-Ogievskiy [this message]
2020-10-22 18:56 ` [PATCH v5 02/12] iotests/303: use dot slash for qcow2.py running Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 03/12] iotests: fix some whitespaces in test output files Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 04/12] iotests/283: make executable Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 05/12] iotests/299: " Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 06/12] iotests/294: add shebang line Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 07/12] iotests: define group in each iotest Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 08/12] iotests: add findtests.py Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 09/12] iotests: add testenv.py Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 10/12] iotests: add testrunner.py Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH v5 11/12] iotests: rewrite check into python Vladimir Sementsov-Ogievskiy
2020-10-22 18:56 ` [PATCH RFC v5 12/12] iotests: rename and move 169 and 199 tests Vladimir Sementsov-Ogievskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201022185627.16987-2-vsementsov@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).