From: Kevin Wolf <kwolf@redhat.com>
To: agraf@suse.de
Cc: gollub@b1-systems.de, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on block_openbsd_4.9
Date: Wed, 07 Mar 2012 10:51:53 +0100 [thread overview]
Message-ID: <4F572FB9.7060902@redhat.com> (raw)
In-Reply-To: <20120307025723.85E3140088@buildbot.b1-systems.de>
Am 07.03.2012 03:57, schrieb qemu@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder block_openbsd_4.9 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/block_openbsd_4.9/builds/148
>
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>
> Buildslave for this Build: kraxel_openbsd49
>
> Build Reason: The Nightly scheduler named 'nightly_block' triggered this build
> Build Source Stamp: [branch block] HEAD
> Blamelist:
>
> BUILD FAILED: failed compile
>
> sincerely,
> -The Buildbot
Hi Alex,
this is a problem with signrom.sh. master has failed in the same way
recently:
AS optionrom/kvmvapic.o
Building optionrom/kvmvapic.img
Building optionrom/kvmvapic.raw
Signing optionrom/kvmvapic.bin
/home/buildbot/slave-public/block_openbsd_4.9/build/scripts/signrom.sh[31]:
018
* 512 - 1 : bad number `018'
gmake[1]: *** [kvmvapic.bin] Error 1
gmake: *** [romsubdir-optionrom] Error 2
Kevin
next prev parent reply other threads:[~2012-03-07 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 2:57 [Qemu-devel] buildbot failure in qemu on block_openbsd_4.9 qemu
2012-03-07 9:51 ` Kevin Wolf [this message]
2012-03-07 11:29 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 0:08 qemu
2012-12-17 0:43 qemu
2012-09-20 6:15 qemu
2012-08-15 1:04 qemu
2012-06-05 1:34 qemu
2012-05-24 1:03 qemu
2012-05-24 12:52 ` Luiz Capitulino
2012-02-20 5:03 qemu
2012-01-24 2:06 qemu
2011-11-23 2:04 qemu
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=4F572FB9.7060902@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=lcapitulino@redhat.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 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).