From: Stefan Hajnoczi <stefanha@redhat.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: peter.maydell@linaro.org, mst@redhat.com, aik@ozlabs.ru,
qemu-devel@nongnu.org, pbonzini@redhat.com,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH for-2.0 V4] tests/acpi-test: do not fail if iasl is broken
Date: Mon, 24 Mar 2014 14:23:36 +0100 [thread overview]
Message-ID: <20140324132336.GG4384@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1395663430.2354.6.camel@localhost.localdomain>
On Mon, Mar 24, 2014 at 02:17:10PM +0200, Marcel Apfelbaum wrote:
> On Mon, 2014-03-24 at 11:33 +0100, Andreas Färber wrote:
> > Am 24.03.2014 11:02, schrieb Marcel Apfelbaum:
> > > There is an issue with iasl on big endian machines: It
> > > cannot disassemble acpi tables taken from little endian
> > > machines, so we cannot check the expected tables.
> > >
> > > The acpi test will check if the expected aml files
> > > can be disassembled, and will issue an warning not
> > > failing the test on those machines until this
> > > problem is solved by the acpica community.
> > >
> > > Signed-off-by: Marcel Apfelbaum <marcel.a@redhat.com>
> > > ---
> > > V3 -> V4:
> > > Addressed all upstream comments:
> > > - Instead of disabling iasl for big endian machines,
> > > the test checks if the expected aml files can be
> > > disassembled, if not it issues a warning instead
> > > of failing the test
> > >
> > > V2 -> V3:
> > > Addressed Michael S. Tsirkin's review:
> > > - tests don't need to re-run detection, use configure
> > > to figure out if it is an LE machine.
> > >
> > > V1 -> V2:
> > > Addressed an offline tip for a much cleaner
> > > macro line, thanks!
> > >
> > > tests/acpi-test.c | 26 +++++++++++++++-----------
> > > 1 file changed, 15 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/tests/acpi-test.c b/tests/acpi-test.c
> > > index 249fe03..76fbccf 100644
> > > --- a/tests/acpi-test.c
> > > +++ b/tests/acpi-test.c
> > > @@ -456,13 +456,12 @@ static bool load_asl(GArray *sdts, AcpiSdtTable *sdt)
> > > /* pass 'out' and 'out_err' in order to be redirected */
> > > ret = g_spawn_command_line_sync(command_line->str, &out, &out_err, NULL, &error);
> > > g_assert_no_error(error);
> > > -
> > > if (ret) {
> > > ret = g_file_get_contents(sdt->asl_file, (gchar **)&sdt->asl,
> > > &sdt->asl_len, &error);
> > > g_assert(ret);
> > > g_assert_no_error(error);
> > > - g_assert(sdt->asl_len);
> > > + ret = (sdt->asl_len > 0);
> > > }
> > >
> > > g_free(out);
> > > @@ -560,15 +559,20 @@ static void test_acpi_asl(test_data *data)
> > > g_assert(!err || exp_err);
> > >
> > > if (g_strcmp0(asl->str, exp_asl->str)) {
> > > - uint32_t signature = cpu_to_le32(exp_sdt->header.signature);
> > > - sdt->tmp_files_retain = true;
> > > - exp_sdt->tmp_files_retain = true;
> > > - fprintf(stderr,
> > > - "acpi-test: Warning! %.4s mismatch. "
> > > - "Actual [asl:%s, aml:%s], Expected [asl:%s, aml:%s].\n",
> > > - (gchar *)&signature,
> > > - sdt->asl_file, sdt->aml_file,
> > > - exp_sdt->asl_file, exp_sdt->aml_file);
> > > + if (exp_err) {
> > > + fprintf(stderr,
> > > + "Warning! iasl couldn't parse the expected aml\n");
> >
> > Should these two be g_test_message()s? That's used in other tests -
> > downside is the message appears in the .xml files generated as
> > intermediary for the HTML report but did (in my case) not show up on
> > stdout/stderr. Maybe we should try to fix that? Paolo? Stefan?
> I also don't see them in stdout/stderr. This is the *only*
> reason I use fprintf.
Did you try running gtester without -q or even with -v? (You can edit
tests/Makefile to do that.)
Stefan
next prev parent reply other threads:[~2014-03-24 13:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 10:02 [Qemu-devel] [PATCH for-2.0 V4] tests/acpi-test: do not fail if iasl is broken Marcel Apfelbaum
2014-03-24 10:33 ` Andreas Färber
2014-03-24 12:17 ` Marcel Apfelbaum
2014-03-24 13:23 ` Stefan Hajnoczi [this message]
2014-03-24 13:24 ` Peter Maydell
2014-03-24 13:29 ` Marcel Apfelbaum
2014-03-24 13:43 ` Marcel Apfelbaum
2014-03-24 13:53 ` Marcel Apfelbaum
2014-03-24 14:26 ` Andreas Färber
2014-03-24 10:42 ` Michael S. Tsirkin
2014-03-24 12:52 ` Andreas Färber
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=20140324132336.GG4384@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=afaerber@suse.de \
--cc=aik@ozlabs.ru \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).