From: Thomas Huth <1916506@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1916506] Re: make check-venv may leave stale and incomplete tests/venv directory directory
Date: Thu, 13 May 2021 12:00:24 -0000 [thread overview]
Message-ID: <162090722440.1405.14629415956737408174.malone@wampee.canonical.com> (raw)
In-Reply-To: 161400927228.11180.7056675088982661405.malonedeb@chaenomeles.canonical.com
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" or "Confirmed" within the next 60 days (other-
wise it will get closed as "Expired"). We will then eventually migrate
the ticket automatically to the new system (but you won't be the reporter
of the bug in the new system and thus you won't get notified on changes
anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1916506
Title:
make check-venv may leave stale and incomplete tests/venv directory
directory
Status in QEMU:
Incomplete
Bug description:
As reported by "Philippe Mathieu-Daudé" <philmd@redhat.com>, a "make
check-venv" can be run and fail to properly create a suitable virtual
environment, leaving the tests/venv directory which is the target for
"make check-venv" itself.
This means that on a subsequent run:
> $ make check-venv
> GIT ui/keycodemapdb tests/fp/berkeley-testfloat-3
> tests/fp/berkeley-softfloat-3 dtc capstone slirp
> make: Nothing to be done for 'check-venv'.
And the venv will still be incomplete. The causes of such failures to
create a suitable virtual environment are too many (in the reported
case it was because of missing *required* Python packages). Some more
evolved virtual environments + Python packaging systems exist that
could probably be used here (Pipenv) but would add further core
requirements.
The current mitigation is to run "make check-clean" when the venv
appears to be incomplete.
The goal of this bug is to attempt to make the venv setup atomic and
more reliable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1916506/+subscriptions
next prev parent reply other threads:[~2021-05-13 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:54 [Bug 1916506] [NEW] make check-venv may leave stale and incomplete tests/venv directory directory Cleber Rosa
2021-02-22 16:08 ` [Bug 1916506] " Philippe Mathieu-Daudé
2021-05-13 12:00 ` Thomas Huth [this message]
2021-07-13 4:17 ` Launchpad Bug Tracker
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=162090722440.1405.14629415956737408174.malone@wampee.canonical.com \
--to=1916506@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.