All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/9] x86 and machine queue, 2017-10-05
Date: Fri, 6 Oct 2017 16:37:48 +0100	[thread overview]
Message-ID: <CAFEAcA94pKm22fX1kCr72-SsM06Z2AMUZ65a7zJ_UPrarkBg1w@mail.gmail.com> (raw)
In-Reply-To: <20171006152751.GR4015@localhost.localdomain>

On 6 October 2017 at 16:27, Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Fri, Oct 06, 2017 at 01:17:42PM +0100, Peter Maydell wrote:
>> This fails tests, I'm afraid:
> [...]
>> acpi-test: Warning! DSDT mismatch. Actual [asl:/tmp/asl-6QYK7Y.dsl,
>> aml:/tmp/aml-E8YK7Y], Expected [asl:/tmp/asl-1H1I7Y.dsl,
>> aml:tests/acpi-test-data/pc/DSDT.memhp].
>> acpi-test: Warning. not showing difference since no diff utility is
>> specified. Set 'DIFF' environment variable to a preferred diff utility
>> and run 'make V=1 check' again to see ASL difference.OK
>>
>> and same for /i386/acpi/piix4/numamem and for the
>> equivalent q35 tests.
>>
>> Fails on s390, netbsd, freebsd, aarch32, x86-64.
>>
>
> Oops, sorry!
>
> I need to find out why it didn't fail on travis-ci:
> https://travis-ci.org/ehabkost/qemu/builds/283884670

My guess is that one of {iasl installed, iasl not installed}
is broken, but the travis environments don't test both.

thanks
-- PMM

  reply	other threads:[~2017-10-06 15:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 20:36 [Qemu-devel] [PULL 0/9] x86 and machine queue, 2017-10-05 Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 1/9] hw/acpi-build: Make assignment statement of next_base easy to read Eduardo Habkost
2017-11-28 15:07   ` Igor Mammedov
2017-11-29  1:07     ` Dou Liyang
2017-10-05 20:36 ` [Qemu-devel] [PULL 2/9] ACPI/unit-test: Add a new testcase for RAM allocation in numa node Eduardo Habkost
2017-11-28 15:08   ` Igor Mammedov
2017-11-29  1:06     ` Dou Liyang
2017-10-05 20:36 ` [Qemu-devel] [PULL 3/9] qom/cpu: move cpu_model null check to cpu_class_by_name() Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 4/9] machine: Add a valid_cpu_types property Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 5/9] vl: Eliminate defconfig variable Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 6/9] qemu-options: Deprecate -nodefconfig Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 7/9] config: qemu_config_parse() return number of config groups Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 8/9] qom: update doc comment for type_register[_static]() Eduardo Habkost
2017-10-05 20:36 ` [Qemu-devel] [PULL 9/9] x86: Correct translation of some rdgsbase and wrgsbase encodings Eduardo Habkost
2017-10-06 12:17 ` [Qemu-devel] [PULL 0/9] x86 and machine queue, 2017-10-05 Peter Maydell
2017-10-06 13:45   ` Thomas Huth
2017-10-06 15:27   ` Eduardo Habkost
2017-10-06 15:37     ` Peter Maydell [this message]
2017-10-10  7:41       ` Dou Liyang
2017-10-10  9:40         ` Peter Maydell
2017-10-10 13:29           ` Dou Liyang
2017-10-10 12:52         ` Eduardo Habkost
2017-10-10 12:56           ` Peter Maydell
2017-10-10 14:17             ` Dou Liyang
2017-10-10 16:03             ` Eduardo Habkost
2017-10-10 13:07           ` Dou Liyang

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=CAFEAcA94pKm22fX1kCr72-SsM06Z2AMUZ65a7zJ_UPrarkBg1w@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=ehabkost@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 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.