From: Gerd Hoffmann <kraxel@gmail.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: buildbot failure in qemu on openbsd-default
Date: Wed, 09 May 2012 10:43:54 +0200 [thread overview]
Message-ID: <4FAA2E4A.5050102@gmail.com> (raw)
In-Reply-To: <20120508173000.A488B40248@spunk.home.kraxel.org>
-------- Original Message --------
Subject: buildbot failure in qemu on openbsd-default
Date: Tue, 08 May 2012 19:30:00 +0200
From: buildbot@spunk.home.kraxel.org
To: kraxel+allbuilders@gmail.com
The Buildbot has detected a failed build on builder openbsd-default
while building qemu.
Full details are available at:
http://www.kraxel.org/bb/builders/openbsd-default/builds/245
Buildbot URL: http://www.kraxel.org/bb/
Buildslave for this Build: openbsd
Build Reason: scheduler
Build Source Stamp: [branch master] 4f08129eeb42422655cc946a0a0c3accc2b8e3db
Blamelist: Alexander Graf <agraf@suse.de>,Alon Levy
<alevy@redhat.com>,Andreas Färber <afaerber@suse.de>,Anthony Liguori
<aliguori@us.ibm.com>,Avi Kivity <avi@redhat.com>,Hervé Poussineau
<hpoussin@reactos.org>,Kevin Wolf <kwolf@redhat.com>,MORITA Kazutaka
<morita.kazutaka@gmail.com>,Paolo Bonzini <pbonzini@redhat.com>,Ronnie
Sahlberg <ronniesahlberg@gmail.com>,Stefan Weil <sw@weilnetz.de>,Zhi
Yong Wu <wuzhy@linux.vnet.ibm.com>
BUILD FAILED: failed test
sincerely,
-The Buildbot
========== log tail ==========
LINK tests/test-coroutine
/usr/local/lib/libglib-2.0.so.2992.0: warning: vsprintf() is often
misused, please use vsnprintf()
/usr/local/lib/libglib-2.0.so.2992.0: warning: stpcpy() is dangerous GNU
crap; don't use it
/usr/local/lib/libglib-2.0.so.2992.0: warning: strcpy() is almost always
misused, please use strlcpy()
/usr/local/lib/libcurl.so.22.0: warning: strcat() is almost always
misused, please use strlcat()
/usr/local/lib/libglib-2.0.so.2992.0: warning: sprintf() is often
misused, please use snprintf()
GTESTER tests/test-coroutine
CC tests/rtc-test.o
CC tests/libqtest.o
LINK tests/rtc-test
/usr/local/lib/libglib-2.0.so.2992.0: warning: vsprintf() is often
misused, please use vsnprintf()
/usr/local/lib/libglib-2.0.so.2992.0: warning: stpcpy() is dangerous GNU
crap; don't use it
/usr/local/lib/libglib-2.0.so.2992.0: warning: strcpy() is almost always
misused, please use strlcpy()
/usr/local/lib/libcurl.so.22.0: warning: strcat() is almost always
misused, please use strlcat()
/usr/local/lib/libglib-2.0.so.2992.0: warning: sprintf() is often
misused, please use snprintf()
CC tests/m48t59-test.o
LINK tests/m48t59-test
/usr/local/lib/libglib-2.0.so.2992.0: warning: vsprintf() is often
misused, please use vsnprintf()
/usr/local/lib/libglib-2.0.so.2992.0: warning: stpcpy() is dangerous GNU
crap; don't use it
/usr/local/lib/libglib-2.0.so.2992.0: warning: strcpy() is almost always
misused, please use strlcpy()
/usr/local/lib/libcurl.so.22.0: warning: strcat() is almost always
misused, please use strlcat()
/usr/local/lib/libglib-2.0.so.2992.0: warning: sprintf() is often
misused, please use snprintf()
GTESTER check-qtest-i386
setitimer: Invalid argument
Internal timer error: aborting
Broken pipe
GTester: last random seed: R02Sf7b54e14382790019cefb3727d8df9dd
setitimer: Invalid argument
Internal timer error: aborting
Broken pipe
GTester: last random seed: R02S645aae24b402acb7d0345cf27f0c15ce
gmake: *** [check-qtest-i386] Error 1
========== full log ==========
http://www.kraxel.org/bb/builders/openbsd-default/builds/245/steps/test/logs/stdio
next parent reply other threads:[~2012-05-09 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120508173000.A488B40248@spunk.home.kraxel.org>
2012-05-09 8:43 ` Gerd Hoffmann [this message]
[not found] <20121101201201.A7F474027F@spunk.home.kraxel.org>
2012-11-02 15:25 ` [Qemu-devel] Fwd: buildbot failure in qemu on openbsd-default Gerd Hoffmann
2012-11-02 16:22 ` Anthony Liguori
2012-11-02 17:53 ` Paolo Bonzini
[not found] <20121115150614.7EF3A400FC@spunk.home.kraxel.org>
2012-11-15 16:08 ` Gerd Hoffmann
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=4FAA2E4A.5050102@gmail.com \
--to=kraxel@gmail.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 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.