From: Cleber Rosa <crosa@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: ldoktor@redhat.com, qemu-devel@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] Cryptic errors from PIP install if missing openssl-devel
Date: Thu, 5 Sep 2019 11:24:37 -0400 [thread overview]
Message-ID: <20190905152437.GA15321@localhost.localdomain> (raw)
In-Reply-To: <20190905140618.GE4617@habkost.net>
On Thu, Sep 05, 2019 at 11:06:18AM -0300, Eduardo Habkost wrote:
> On Thu, Sep 05, 2019 at 09:38:24AM -0400, Cleber Rosa wrote:
> > On Thu, Sep 05, 2019 at 12:09:24PM +1000, David Gibson wrote:
> > > On Wed, Sep 04, 2019 at 03:57:17PM -0400, Cleber Rosa wrote:
> > > >
> > > > Hi David,
> > > >
> > > > I've pushed a branch here (most of the commits have already been sent
> > > > separately):
> > > >
> > > > https://github.com/clebergnu/qemu/tree/ppc64
> > > >
> > > > I've tested on a RHEL 8 ppc64le Power 9, and it seems to work for me.
> > > > My steps for building QEMU:
> > > >
> > > > - Configured with: '/home/cleber/src/qemu/configure' '--enable-slirp=git' '--python=/usr/bin/python3' '--target-list=x86_64-softmmu,ppc64-softmmu,arm-softmmu,aarch64-softmmu,mips-softmmu,mipsel-softmmu,mips64-softmmu,mips64el-softmmu,sh4-softmmu,s390x-softmmu,alpha-softmmu,m68k-softmmu,riscv64-softmmu'
> > > > - make
> > > > - make check-acceptance
> > > >
> > > > Would you be able to test if that branch works smoothly for you?
> > >
> > > So, with this tree I'm no longer getting problems if openssl-devel is
> > > not installed, so that much looks good.
> > >
> > > I am getting some different errors - I was seeing this before (with
> > > openssl-devel installed) sometimes, but only sometimes. I haven't yet
> > > worked out a pattern for when they appeared. They also don't appear
> > > to be fatal, the rest of the tests seem to be running ok. Any ideas?
> > >
> > > VENV /home/dwg/qemu/build/rhel8/tests/venv
> > > PIP /home/dwg/qemu/tests/requirements.txt
> > > AVOCADO tests/acceptance
> > > Error running method "run" of plugin "html": 'Namespace' object has no attribute 'get'
> > > Error running method "run" of plugin "varianter_cit": 'Namespace' object has no attribute 'get'
> >
> > Hi David,
> >
> > Yes, those should not be fatal. Anyway, they are caused by two things:
> >
> > 1) A second set of Avocado plugins installation with different versions
> > than the Avocado installation on QEMU's tests venv
> >
> > 2) The tests' venv, which is created with "--system-site-packages",
> > option that is described as "Give the virtual environment access
> > to the system site-packages dir."
> >
> > The motivation to have "--system-site-packages" is that, if the user
> > had any of the "requirements.txt" depedencies installed system wide,
> > the venv would simply use it and skip downloads. Maybe we should make
> > that an optional feature, disabled by default, so that the test's venv
> > is better isolated and more predictable by default.
> >
> > Eduardo,
> >
> > I remember we discussed #2, so your opinion is appreciated here.
>
> I think I was the person who insisted for --system-site-packages.
> Considering that we're often using very recent versions of
> Avocado, maybe trying to use system-provided Avocado modules by
> default wasn't a good idea after all.
>
> Making --system-site-packages optional and not enabling it by
> default sounds like a reasonable workaround.
>
OK, agreed.
FIY, given the fact that pip itself keeps a local cache, not using
"--system-site-packages" this shouldn't be much of a hit when it
comes to downloads.
Cheers,
- Cleber.
> --
> Eduardo
>
next prev parent reply other threads:[~2019-09-05 15:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 1:31 [Qemu-devel] Cryptic errors from PIP install if missing openssl-devel David Gibson
2019-08-29 1:51 ` David Gibson
2019-08-29 3:27 ` Cleber Rosa
2019-08-29 9:24 ` Philippe Mathieu-Daudé
2019-08-29 9:46 ` Philippe Mathieu-Daudé
2019-09-03 15:08 ` Cleber Rosa
2019-09-03 15:22 ` Philippe Mathieu-Daudé
2019-09-03 15:47 ` Cleber Rosa
2019-09-03 15:56 ` Lukáš Doktor
2019-09-03 15:57 ` Lukáš Doktor
2019-09-03 17:27 ` Eduardo Habkost
2019-09-03 22:33 ` Cleber Rosa
2019-09-03 15:18 ` Cleber Rosa
2019-08-30 17:56 ` Eduardo Habkost
2019-08-31 1:48 ` David Gibson
2019-09-03 15:31 ` Cleber Rosa
2019-09-04 19:57 ` Cleber Rosa
2019-09-05 2:09 ` David Gibson
2019-09-05 13:38 ` Cleber Rosa
2019-09-05 14:06 ` Eduardo Habkost
2019-09-05 15:24 ` Cleber Rosa [this message]
2019-09-06 0:34 ` David Gibson
2019-09-06 14:43 ` Eduardo Habkost
2019-09-06 14:52 ` Cleber Rosa
2019-09-06 15:14 ` Eduardo Habkost
2019-09-06 15:29 ` Cleber Rosa
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=20190905152437.GA15321@localhost.localdomain \
--to=crosa@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=ldoktor@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).