From: no-reply@patchew.org
To: ehabkost@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, borntraeger@de.ibm.com,
libvir-list@redhat.com, dahi@linux.vnet.ibm.com,
cornelia.huck@de.ibm.com, imammedo@redhat.com,
jdenemar@redhat.com
Subject: Re: [Qemu-devel] [libvirt] [PATCH v3 0/5] Add runnability info to query-cpu-definitions
Date: Mon, 19 Sep 2016 14:16:18 -0700 (PDT) [thread overview]
Message-ID: <20160919211615.19907.24021@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1474314175-24374-1-git-send-email-ehabkost@redhat.com>
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [libvirt] [PATCH v3 0/5] Add runnability info to query-cpu-definitions
Message-id: 1474314175-24374-1-git-send-email-ehabkost@redhat.com
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
make J=8 docker-test-quick@centos6
make J=8 docker-test-mingw@fedora
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
From https://github.com/patchew-project/qemu
* [new tag] patchew/1474314175-24374-1-git-send-email-ehabkost@redhat.com -> patchew/1474314175-24374-1-git-send-email-ehabkost@redhat.com
* [new tag] patchew/c1a178ce-1c5e-2c26-0f55-6a4fbfe21a83@tuxfamily.org -> patchew/c1a178ce-1c5e-2c26-0f55-6a4fbfe21a83@tuxfamily.org
Switched to a new branch 'test'
43f49c7 target-i386: Return runnability information on query-cpu-definitions
17a9434 qmp: Add runnability information to query-cpu-definitions
405e270 target-i386: Define CPUID filtering functions before x86_cpu_list()
dc099e7 target-i386: Move warning code outside x86_cpu_filter_features()
21da10b target-i386: List CPU models using subclass list
=== OUTPUT BEGIN ===
Submodule 'dtc' (git://git.qemu-project.org/dtc.git) registered for path 'dtc'
Cloning into 'dtc'...
Submodule path 'dtc': checked out '65cc4d2748a2c2e6f27f1cf39e07a5dbabd80ebf'
BUILD centos6
=== OUTPUT END ===
Abort: command timeout (>3600 seconds)
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@freelists.org
prev parent reply other threads:[~2016-09-19 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 19:42 [Qemu-devel] [PATCH v3 0/5] Add runnability info to query-cpu-definitions Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 1/5] target-i386: List CPU models using subclass list Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 2/5] target-i386: Move warning code outside x86_cpu_filter_features() Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 3/5] target-i386: Define CPUID filtering functions before x86_cpu_list() Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 4/5] qmp: Add runnability information to query-cpu-definitions Eduardo Habkost
2016-09-20 18:25 ` [Qemu-devel] [libvirt] " Eric Blake
2016-09-20 19:05 ` Eduardo Habkost
2016-09-19 19:42 ` [Qemu-devel] [PATCH v3 5/5] target-i386: Return runnability information on query-cpu-definitions Eduardo Habkost
2016-09-19 21:16 ` 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=20160919211615.19907.24021@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=imammedo@redhat.com \
--cc=jdenemar@redhat.com \
--cc=libvir-list@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).