qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <marcel.a@redhat.com>
Subject: [Qemu-devel] [PATCH] tests: require that acpi tests are enabled explicitly
Date: Thu, 16 Jan 2014 13:08:14 +0200	[thread overview]
Message-ID: <20140116110814.GA28948@redhat.com> (raw)

ACPI code is changing as bit too fast to make
it worth it to require everyone to check
it against expected output.
Make test run depend on an ACPI_TEST_EXPECTED_AML
set in environment, so interested people can
run it without affecting everyone.

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---

I'd like to prevent tests failing for everyone each time
we change some ACPI code.
This is an inelegant way to do this, would be better to emit
a warning and keep going.

 tests/acpi-test.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/tests/acpi-test.c b/tests/acpi-test.c
index b5ab70a..c164382 100644
--- a/tests/acpi-test.c
+++ b/tests/acpi-test.c
@@ -22,6 +22,7 @@
 #define MACHINE_PC "pc"
 #define MACHINE_Q35 "q35"
 
+#define ACPI_TEST_EXPECTED_AML "TEST_ACPI_TEST_AML"
 #define ACPI_REBUILD_EXPECTED_AML "TEST_ACPI_REBUILD_AML"
 
 /* DSDT and SSDTs format */
@@ -572,7 +573,10 @@ static void test_acpi_one(const char *params, test_data *data)
     test_acpi_dsdt_table(data);
     test_acpi_ssdt_tables(data);
 
-    if (iasl) {
+    if (getenv(ACPI_TEST_EXPECTED_AML)) {
+
+        g_assert(iasl);
+
         if (getenv(ACPI_REBUILD_EXPECTED_AML)) {
             dump_aml_files(data, true);
         } else {
-- 
MST

                 reply	other threads:[~2014-01-16 11:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140116110814.GA28948@redhat.com \
    --to=mst@redhat.com \
    --cc=marcel.a@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).