From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Maydell Peter <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>, Thomas Huth <thuth@redhat.com>,
Igor M <imammedo@redhat.com>, Michael Tsirkin <mst@redhat.com>
Subject: Re: [PATCH v3 00/10] Introduce new acpi/smbios avocado tests using biosbits
Date: Mon, 10 Oct 2022 10:20:08 +0100 [thread overview]
Message-ID: <Y0PjyANuojwEypoc@redhat.com> (raw)
In-Reply-To: <CAARzgwwKthMvty72SkG_zt9rpuAek-PMS3+aK9dUKS_e50EDxA@mail.gmail.com>
On Mon, Oct 10, 2022 at 01:43:21PM +0530, Ani Sinha wrote:
> On Mon, Oct 10, 2022 at 1:24 PM Ani Sinha <ani@anisinha.ca> wrote:
> >
> > Please see the README file added in patch 10 for more details.
> > Sample runs are as follows:
> >
> > $ ./tests/venv/bin/avocado run -t acpi tests/avocado --tap -
> > ERROR: Missing parentheses in call to 'print'. Did you mean print(...)? (smbios.py, line 92)
> > ERROR: Missing parentheses in call to 'print'. Did you mean print(...)? (smilatency.py, line 47)
> > ERROR: Missing parentheses in call to 'print'. Did you mean print(...)? (testacpi.py, line 158)
>
> None of the above files are avocado tests or avocado related python
> scripts. They are run from within bits in a python 2.7 environment. I
> could not find a mechanism to exclude a directory from avocado tests.
> I also do not think making those scripts python 3 compliant is a good
> use of my time since upgrading bits to use python 3 would be a major
> task unrelated to QEMU testing.
In one of the later patches copy_test_scripts() copies the files
into the guest image IIUC.
If you rename them in git, to be .py2 then presumably avocado
wont try to load them, and then in copy_test_scripts you can
give them the normal .py extension for the guest. The .py2
extension will also make it more obvious to maintainers that
these are different from the rest of the python coded we have.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-10-10 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 7:54 [PATCH v3 00/10] Introduce new acpi/smbios avocado tests using biosbits Ani Sinha
2022-10-10 8:13 ` Ani Sinha
2022-10-10 8:56 ` Thomas Huth
2022-10-10 9:13 ` Ani Sinha
2022-10-10 9:21 ` Thomas Huth
2022-10-10 9:20 ` Daniel P. Berrangé [this message]
2022-10-10 9:36 ` Ani Sinha
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=Y0PjyANuojwEypoc@redhat.com \
--to=berrange@redhat.com \
--cc=ani@anisinha.ca \
--cc=imammedo@redhat.com \
--cc=jsnow@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).