From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>, "Fam Zheng" <famz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 1/3] device-crash-test: No need for sys.path hack
Date: Mon, 18 Jun 2018 19:51:29 -0300 [thread overview]
Message-ID: <20180618225131.13113-2-ehabkost@redhat.com> (raw)
In-Reply-To: <20180618225131.13113-1-ehabkost@redhat.com>
The device-crash-test script is already inside the 'scripts'
directory, there's no need to add the directory manually to
sys.path.
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
scripts/device-crash-test | 1 -
1 file changed, 1 deletion(-)
diff --git a/scripts/device-crash-test b/scripts/device-crash-test
index e6c233e9bf..52a2a613d4 100755
--- a/scripts/device-crash-test
+++ b/scripts/device-crash-test
@@ -35,7 +35,6 @@ import random
import argparse
from itertools import chain
-sys.path.append(os.path.join(os.path.dirname(__file__), '..', 'scripts'))
from qemu import QEMUMachine
logger = logging.getLogger('device-crash-test')
--
2.18.0.rc1.1.g3f1ff2140
next prev parent reply other threads:[~2018-06-18 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 22:51 [Qemu-devel] [PATCH 0/3] python: Revert sys.path hacks used for compat modules Eduardo Habkost
2018-06-18 22:51 ` Eduardo Habkost [this message]
2018-06-19 8:54 ` [Qemu-devel] [PATCH 1/3] device-crash-test: No need for sys.path hack Daniel P. Berrangé
2018-06-18 22:51 ` [Qemu-devel] [PATCH 2/3] Revert "docker.py: Python 2.6 argparse compatibility" Eduardo Habkost
2018-06-19 8:55 ` Daniel P. Berrangé
2018-06-18 22:51 ` [Qemu-devel] [PATCH 3/3] Revert "tests: migration/guestperf " Eduardo Habkost
2018-06-19 8:55 ` Daniel P. Berrangé
2018-06-19 0:41 ` [Qemu-devel] [PATCH 0/3] python: Revert sys.path hacks used for compat modules no-reply
2018-06-20 15:39 ` Stefan Hajnoczi
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=20180618225131.13113-2-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).