From: Paolo Bonzini <pbonzini@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, jsnow@redhat.com
Subject: Re: [PATCH] tests: respect --enable/--disable-download for Avocado
Date: Fri, 10 Nov 2023 11:55:41 +0100 [thread overview]
Message-ID: <CABgObfaROkW3f+YNmFLSN5rKX9BW197aPM2gBXPqx+1t34-GkA@mail.gmail.com> (raw)
In-Reply-To: <95788d03-b854-996c-b8e3-981c79a1bb6c@eik.bme.hu>
On Fri, Nov 10, 2023 at 11:00 AM BALATON Zoltan <balaton@eik.bme.hu> wrote:
> > +if test "$download" = "enabled" ; then
> > + mkvenv_online_flag=" --online"
>
> Is leading space before -- intended? It does not seem to matter at usees
> below.
Maybe it's paranoia but I was worried that some shells would mess up
"echo --foo". They did in the past, but it was many years ago. It would
be useful to add a
print() {
printf '%s\n' "$*"
}
shell function but this was not the right patch to do it.
Paolo
> Regards,
> BALATON Zolatn
>
> > fi
> >
> > if test "$docs" != "disabled" ; then
> > if ! $mkvenv ensuregroup \
> > - $mkvenv_flags \
> > + $(test "$docs" = "enabled" && echo "$mkvenv_online_flag") \
> > ${source_path}/pythondeps.toml docs;
> > then
> > if test "$docs" = "enabled" ; then
> > @@ -1631,6 +1631,7 @@ if test "$container" != no; then
> > fi
> > echo "SUBDIRS=$subdirs" >> $config_host_mak
> > echo "PYTHON=$python" >> $config_host_mak
> > +echo "MKVENV_ENSUREGROUP=$mkvenv ensuregroup $mkvenv_online_flag" >> $config_host_mak
> > echo "GENISOIMAGE=$genisoimage" >> $config_host_mak
> > echo "MESON=$meson" >> $config_host_mak
> > echo "NINJA=$ninja" >> $config_host_mak
> > diff --git a/tests/Makefile.include b/tests/Makefile.include
> > index dab1989a071..c9d1674bd07 100644
> > --- a/tests/Makefile.include
> > +++ b/tests/Makefile.include
> > @@ -111,7 +111,7 @@ quiet-venv-pip = $(quiet-@)$(call quiet-command-run, \
> >
> > $(TESTS_VENV_TOKEN): $(SRC_PATH)/pythondeps.toml
> > $(call quiet-venv-pip,install -e "$(SRC_PATH)/python/")
> > - $(PYTHON) python/scripts/mkvenv.py ensuregroup --online $< avocado
> > + $(MKVENV_ENSUREGROUP) $< avocado
> > $(call quiet-command, touch $@)
> >
> > $(TESTS_RESULTS_DIR):
> >
>
prev parent reply other threads:[~2023-11-10 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 9:33 [PATCH] tests: respect --enable/--disable-download for Avocado Paolo Bonzini
2023-11-10 10:01 ` BALATON Zoltan
2023-11-10 10:55 ` Paolo Bonzini [this message]
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=CABgObfaROkW3f+YNmFLSN5rKX9BW197aPM2gBXPqx+1t34-GkA@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=jsnow@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).