qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: no-reply@patchew.org
To: rutu.shah.26@gmail.com
Cc: famz@redhat.com, qemu-devel@nongnu.org, stefanha@gmail.com,
	edgar.iglesias@gmail.com, qemu-arm@nongnu.org,
	alistair.francis@xilinx.com
Subject: Re: [Qemu-devel] [PATCHv2] Reducing stack frame size in stream_process_mem2s()
Date: Tue, 4 Oct 2016 13:50:33 -0700 (PDT)	[thread overview]
Message-ID: <20161004205031.498194.11825@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <1475604703-3381-1-git-send-email-rutu.shah.26@gmail.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: 1475604703-3381-1-git-send-email-rutu.shah.26@gmail.com
Subject: [Qemu-devel] [PATCHv2] Reducing stack frame size in stream_process_mem2s()

=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
make J=8 docker-test-quick@centos6
make J=8 docker-test-mingw@fedora
=== TEST SCRIPT END ===

Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Switched to a new branch 'test'
4276ebf Reducing stack frame size in stream_process_mem2s()

=== 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

  reply	other threads:[~2016-10-04 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 18:11 [Qemu-devel] [PATCHv2] Reducing stack frame size in stream_process_mem2s() rutu.shah.26
2016-10-04 20:50 ` no-reply [this message]
2016-10-04 20:56 ` Edgar E. Iglesias
2016-10-05 15:59   ` Alistair Francis
2016-10-05 14:07 ` Stefan Hajnoczi

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=20161004205031.498194.11825@ex-std-node742.prod.rhcloud.com \
    --to=no-reply@patchew.org \
    --cc=alistair.francis@xilinx.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=famz@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rutu.shah.26@gmail.com \
    --cc=stefanha@gmail.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).