From: no-reply@patchew.org
To: peterx@redhat.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, mst@redhat.com,
jasowang@redhat.com, vkaplans@redhat.com,
alex.williamson@redhat.com, wexu@redhat.com, pbonzini@redhat.com,
cornelia.huck@de.ibm.com, dgibson@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/3] Introduce IOMMUNotifier struct
Date: Thu, 8 Sep 2016 21:05:43 -0700 (PDT) [thread overview]
Message-ID: <20160909040541.76034.99843@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1473389864-19694-1-git-send-email-peterx@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.
Type: series
Message-id: 1473389864-19694-1-git-send-email-peterx@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/3] Introduce IOMMUNotifier struct
=== 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/1473389864-19694-1-git-send-email-peterx@redhat.com -> patchew/1473389864-19694-1-git-send-email-peterx@redhat.com
Switched to a new branch 'test'
639dbf6 intel_iommu: allow UNMAP notifiers
16bcaf3 memory: introduce IOMMUOps.notify_flag_changed
063de83 memory: introduce IOMMUNotifier and its caps
=== 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
ARCHIVE qemu.tgz
ARCHIVE dtc.tgz
COPY RUNNER
RUN test-quick in 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
next prev parent reply other threads:[~2016-09-09 4:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 2:57 [Qemu-devel] [PATCH v4 0/3] Introduce IOMMUNotifier struct Peter Xu
2016-09-09 2:57 ` [Qemu-devel] [PATCH v4 1/3] memory: introduce IOMMUNotifier and its caps Peter Xu
2016-09-14 5:48 ` David Gibson
2016-09-14 7:15 ` David Gibson
2016-09-14 7:40 ` Peter Xu
2016-09-14 10:47 ` David Gibson
2016-09-14 8:17 ` Peter Xu
2016-09-14 10:50 ` David Gibson
2016-09-09 2:57 ` [Qemu-devel] [PATCH v4 2/3] memory: introduce IOMMUOps.notify_flag_changed Peter Xu
2016-09-14 5:55 ` David Gibson
2016-09-14 7:12 ` Peter Xu
2016-09-14 7:22 ` David Gibson
2016-09-14 7:49 ` Peter Xu
2016-09-14 10:37 ` David Gibson
2016-09-14 11:25 ` Peter Xu
2016-09-09 2:57 ` [Qemu-devel] [PATCH v4 3/3] intel_iommu: allow UNMAP notifiers Peter Xu
2016-09-14 5:56 ` David Gibson
2016-09-09 4:05 ` no-reply [this message]
2016-09-09 6:41 ` [Qemu-devel] [PATCH v4 0/3] Introduce IOMMUNotifier struct Peter Xu
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=20160909040541.76034.99843@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=alex.williamson@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dgibson@redhat.com \
--cc=famz@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkaplans@redhat.com \
--cc=wexu@redhat.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 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.