From: no-reply@patchew.org
To: ehabkost@redhat.com
Cc: ehabkost@redhat.com, qemu-devel@nongnu.org, babu.moger@amd.com,
imammedo@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/2] i386: Introduce X86CPUCacheCPUID struct
Date: Thu, 20 Jun 2019 14:31:10 -0700 (PDT) [thread overview]
Message-ID: <156106626908.29212.2766222596090316863@ce79690b2cb9> (raw)
In-Reply-To: <20190620203616.22715-1-ehabkost@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190620203616.22715-1-ehabkost@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
make docker-image-fedora V=1 NETWORK=1
time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1
=== TEST SCRIPT END ===
CC x86_64-softmmu/target/i386/svm_helper.o
CC x86_64-softmmu/target/i386/machine.o
CC x86_64-softmmu/target/i386/arch_memory_mapping.o
/tmp/qemu-test/src/target/i386/cpu.c:1484:15: error: initializer element is not a compile-time constant
.cpuid2 = epyc_cache_info,
^~~~~~~~~~~~~~~
1 error generated.
The full log is available at
http://patchew.org/logs/20190620203616.22715-1-ehabkost@redhat.com/testing.asan/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
prev parent reply other threads:[~2019-06-20 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 20:36 [Qemu-devel] [PATCH 0/2] i386: Introduce X86CPUCacheCPUID struct Eduardo Habkost
2019-06-20 20:36 ` [Qemu-devel] [PATCH 1/2] i386: make cache structs const-safe Eduardo Habkost
2019-06-20 20:36 ` [Qemu-devel] [PATCH 2/2] i386: Introduce X86CPUCacheCPUID struct Eduardo Habkost
2019-06-20 21:31 ` no-reply [this message]
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=156106626908.29212.2766222596090316863@ce79690b2cb9 \
--to=no-reply@patchew.org \
--cc=babu.moger@amd.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).