From: "Philippe Mathieu-Daudé via" <qemu-devel@nongnu.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Yang Zhong" <yang.zhong@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Igor Mammedov" <imammedo@redhat.com>
Subject: Re: [PATCH v3 1/2] hw/i386: Attach CPUs to machine
Date: Sat, 5 Feb 2022 11:32:19 +0100 [thread overview]
Message-ID: <f4544f90-4fb4-dfad-48ef-8631cf3c7666@amsat.org> (raw)
In-Reply-To: <CABgObfb8EQxObAnBJKSq=OMCFhkL7FzNFCn1H=HoCyxz03R2Fw@mail.gmail.com>
+Igor
On 5/2/22 10:21, Paolo Bonzini wrote:
> It broke check-system-debian in CI.
OK. This is odd because I am using Ubuntu 20.04 x86_64 host and
can not reproduce. I'll investigate.
> Il ven 4 feb 2022, 20:31 Philippe Mathieu-Daudé <f4bug@amsat.org
> <mailto:f4bug@amsat.org>> ha scritto:
>
> On 4/2/22 18:59, Paolo Bonzini wrote:
> > This is causing breakage in the acpi-tables-test, sorry.
>
> $ make check-qtest-x86_64
>
> Ok: 49
> Expected Fail: 0
> Fail: 0
> Unexpected Pass: 0
> Skipped: 7
> Timeout: 0
>
> $ make check-qtest-i386
>
> Ok: 52
> Expected Fail: 0
> Fail: 0
> Unexpected Pass: 0
> Skipped: 4
> Timeout: 0
>
> I am confuse, how do you run it?
>
next prev parent reply other threads:[~2022-02-05 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 23:35 [PATCH v3 0/2] hw/i386: QOM-attach CPUs/SGX-EPC objects to their parents Philippe Mathieu-Daudé via
2022-01-31 23:35 ` [PATCH v3 1/2] hw/i386: Attach CPUs to machine Philippe Mathieu-Daudé via
2022-02-01 9:24 ` Daniel P. Berrangé
2022-02-04 17:59 ` Paolo Bonzini
2022-02-04 19:31 ` Philippe Mathieu-Daudé via
2022-02-05 9:21 ` Paolo Bonzini
2022-02-05 10:32 ` Philippe Mathieu-Daudé via [this message]
2022-02-05 12:48 ` Philippe Mathieu-Daudé via
2022-01-31 23:35 ` [PATCH v3 2/2] hw/i386/sgx: Attach SGX-EPC objects " Philippe Mathieu-Daudé via
2022-02-01 9:25 ` Daniel P. Berrangé
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=f4544f90-4fb4-dfad-48ef-8631cf3c7666@amsat.org \
--to=qemu-devel@nongnu.org \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=richard.henderson@linaro.org \
--cc=yang.zhong@intel.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).