qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: P J P <ppandit@redhat.com>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, peter.maydell@linaro.org, qemu-arm@nongnu.org,
	liqiang6-s@360.cn
Subject: Re: [Qemu-devel] [PATCH v4] timer: a9gtimer: remove loop to auto-increment comparator
Date: Tue, 11 Oct 2016 22:44:28 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.2.20.1610112238260.7380@wniryva> (raw)
In-Reply-To: <20161011000558.498195.49291@ex-std-node742.prod.rhcloud.com>

+-- On Mon, 10 Oct 2016, no-reply@ec2-52-6-146-230.compute-1.amazonaws.com wrote --+
| 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.

  I tried to build it locally(without docker), cloned submodule 'dtc' and used 
the same './configure' options as in the test. It built okay, no error.

| === 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 ===
| 
|   CC      hw/timer/arm_timer.o
|   CC      hw/timer/arm_mptimer.o
|   CC      hw/timer/a9gtimer.o

  It seems to build okay.
 
| (gtester:6328): GLib-WARNING **: Failed to execute test binary: tests/test-qmp-output-visitor: Failed to fork (Resource temporarily unavailable)
| /bin/sh: fork: retry: Resource temporarily unavailable
| make: vfork: Resource temporarily unavailable

  This seems like a system issue, not related to the 'a9gtimer.c' patch.

--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F

  reply	other threads:[~2016-10-11 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08  5:04 [Qemu-devel] [PATCH v4] timer: a9gtimer: remove loop to auto-increment comparator P J P
2016-10-11  0:06 ` no-reply
2016-10-11 17:14   ` P J P [this message]
2016-10-12  1:00     ` Fam Zheng
2016-10-12 12:31 ` Peter Maydell
2016-10-13  6:42   ` P J P
2016-10-13 10:44     ` Peter Maydell
2016-10-13 20:13       ` P J P

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=alpine.LFD.2.20.1610112238260.7380@wniryva \
    --to=ppandit@redhat.com \
    --cc=famz@redhat.com \
    --cc=liqiang6-s@360.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).