From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Subject: [AUTOTEST] Autotest spinning during testing
Date: Tue, 04 Aug 2009 15:21:55 +0300 [thread overview]
Message-ID: <4A7827E3.3010603@redhat.com> (raw)
I see autotest consuming all available cpu after upgrading to
479db4e7c6; strace shows
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
read(23, ""..., 1) = 0
Where 23 is some pipe.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2009-08-04 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 12:21 Avi Kivity [this message]
2009-08-04 14:32 ` [AUTOTEST] Autotest spinning during testing Lucas Meneghel Rodrigues
2009-08-04 15:48 ` Lucas Meneghel Rodrigues
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=4A7827E3.3010603@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.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