From: no-reply@patchew.org
To: kraxel@redhat.com
Cc: kraxel@redhat.com, qemu-devel@nongnu.org, flier_m@outlook.com,
mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] ati: fix ati_cursor_define bug.
Date: Tue, 17 Sep 2019 09:22:38 -0700 (PDT) [thread overview]
Message-ID: <156873735697.17151.14736504340945340177@5dec9699b7de> (raw)
In-Reply-To: <20190917111441.27405-1-kraxel@redhat.com>
Patchew URL: https://patchew.org/QEMU/20190917111441.27405-1-kraxel@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 ===
./tests/docker/docker.py --engine auto build qemu:fedora tests/docker/dockerfiles/fedora.docker --add-current-user
Image is up to date.
LD docker-test-debug@fedora.mo
cc: fatal error: no input files
compilation terminated.
make: *** [docker-test-debug@fedora.mo] Error 4
The full log is available at
http://patchew.org/logs/20190917111441.27405-1-kraxel@redhat.com/testing.asan/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2019-09-17 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 11:14 [Qemu-devel] [PATCH v3 0/2] ati: fix ati_cursor_define bug Gerd Hoffmann
2019-09-17 11:14 ` [Qemu-devel] [PATCH v3 1/2] vga: move access helpers to separate include file Gerd Hoffmann
2019-09-17 16:35 ` Philippe Mathieu-Daudé
2019-09-17 11:14 ` [Qemu-devel] [PATCH v3 2/2] ati: use vga_read_byte in ati_cursor_define Gerd Hoffmann
2019-09-17 13:48 ` BALATON Zoltan
2019-09-17 16:37 ` Philippe Mathieu-Daudé
2019-09-17 16:22 ` no-reply [this message]
2019-09-17 16:23 ` [Qemu-devel] [PATCH v3 0/2] ati: fix ati_cursor_define bug no-reply
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=156873735697.17151.14736504340945340177@5dec9699b7de \
--to=no-reply@patchew.org \
--cc=flier_m@outlook.com \
--cc=kraxel@redhat.com \
--cc=mst@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).