From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org, Cleber Rosa <crosa@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: "Aleksandar Markovic" <aleksandar.markovic@rt-rk.com>,
"Aleksandar Rikalo" <arikalo@wavecomp.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH] tests/acceptance: Do not install paramiko module by default
Date: Fri, 30 Aug 2019 20:40:33 +0200 [thread overview]
Message-ID: <20190830184033.7630-1-philmd@redhat.com> (raw)
The paramiko Python module has many dependencies. Some of them
are not pure Python, such cryptography module which requires to
be built and linked with OpenSSL.
When native libraries and header are missing on the host, the
error reported is not very helpful:
$ make check-venv
VENV tests/venv
PIP tests/requirements.txt
Command "tests/venv/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-la4el5r5/cryptography/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-1efs22iz-record/install-record.txt --single-version-externally-managed --compile --install-headers tests/venv/include/site/python3.6/cryptography" failed with error code 1 in /tmp/pip-build-la4el5r5/cryptography/
Since currently the tests depending on paramiko are targetting
very specific uses, we can avoid the strong dependency on the
paramiko module, to let systems where it does not build properly
work the rest of the tests.
If paramiko is manually installed, the tests using it will be
automatically run.
Fixes: c47c336e870
Reported-by: David Gibson <david@gibson.dropbear.id.au>
Suggested-by: Cleber Rosa <crosa@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
tests/acceptance/linux_ssh_mips_malta.py | 13 +++++++++++--
tests/requirements.txt | 1 -
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/tests/acceptance/linux_ssh_mips_malta.py b/tests/acceptance/linux_ssh_mips_malta.py
index aafb0c39f6..dbcdc03a80 100644
--- a/tests/acceptance/linux_ssh_mips_malta.py
+++ b/tests/acceptance/linux_ssh_mips_malta.py
@@ -9,14 +9,19 @@ import os
import re
import base64
import logging
-import paramiko
import time
-from avocado import skipIf
+from avocado import skipIf, skipUnless
from avocado_qemu import Test
from avocado.utils import process
from avocado.utils import archive
+PARAMIKO_AVAILABLE = True
+try:
+ import paramiko
+except ImportError:
+ PARAMIKO_AVAILABLE = False
+
class LinuxSSH(Test):
@@ -171,6 +176,7 @@ class LinuxSSH(Test):
self.run_common_commands()
self.shutdown_via_ssh()
+ @skipUnless(PARAMIKO_AVAILABLE, "paramiko module not available")
@skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
def test_mips_malta32eb_kernel3_2_0(self):
"""
@@ -186,6 +192,7 @@ class LinuxSSH(Test):
self.do_test_mips_malta('be', kernel_path, 'mips')
+ @skipUnless(PARAMIKO_AVAILABLE, "paramiko module not available")
@skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
def test_mips_malta32el_kernel3_2_0(self):
"""
@@ -201,6 +208,7 @@ class LinuxSSH(Test):
self.do_test_mips_malta('le', kernel_path, 'mips')
+ @skipUnless(PARAMIKO_AVAILABLE, "paramiko module not available")
@skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
def test_mips_malta64eb_kernel3_2_0(self):
"""
@@ -215,6 +223,7 @@ class LinuxSSH(Test):
kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
self.do_test_mips_malta('be', kernel_path, 'mips64')
+ @skipUnless(PARAMIKO_AVAILABLE, "paramiko module not available")
@skipIf(os.getenv('CONTINUOUS_INTEGRATION'), 'Running on Travis-CI')
def test_mips_malta64el_kernel3_2_0(self):
"""
diff --git a/tests/requirements.txt b/tests/requirements.txt
index 3ae0e29ad7..002ded6a22 100644
--- a/tests/requirements.txt
+++ b/tests/requirements.txt
@@ -2,4 +2,3 @@
# in the tests/venv Python virtual environment. For more info,
# refer to: https://pip.pypa.io/en/stable/user_guide/#id1
avocado-framework==68.0
-paramiko
--
2.20.1
next reply other threads:[~2019-08-30 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 18:40 Philippe Mathieu-Daudé [this message]
2019-08-30 18:51 ` [Qemu-devel] [PATCH] tests/acceptance: Do not install paramiko module by default Eduardo Habkost
2019-08-31 1:05 ` David Gibson
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=20190830184033.7630-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--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).