From: Gerd Hoffmann <kraxel@redhat.com>
To: berendt@b1-systems.de
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [buildbot patch 0/6] buildbot update
Date: Fri, 1 Feb 2013 15:02:19 +0100 [thread overview]
Message-ID: <1359727345-10477-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Goes on top of stefans update. Untested. Shoveling
over some goodies from my local buildbot config.
https://github.com/kraxel/buildbot/tree/kraxel
(will create a pull req in a moment)
One question on the buildslave config (which isn't in the tree for
security reasons): Do you have max_builds=1 in there, i.e. like
this:
c['slaves'].append(BuildSlave("rhel6.xenb", "idonttellyoumypasswd", max_builds=1))
This makes sure buildbot runs at most a single build per buildslave,
and I think this would make the slow_lock obsolete ...
cheers,
Gerd
Gerd Hoffmann (6):
add linebreaks to make create_build_factory more readable
make tests configurable
fix out-of-tree build
use --disable-debug-info
save config.log
add log tail to failure reports
qemu-master.cfg | 58 +++++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 52 insertions(+), 6 deletions(-)
--
1.7.9.7
next reply other threads:[~2013-02-01 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 14:02 Gerd Hoffmann [this message]
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 1/6] add linebreaks to make create_build_factory more readable Gerd Hoffmann
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 2/6] make tests configurable Gerd Hoffmann
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 3/6] fix out-of-tree build Gerd Hoffmann
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 4/6] use --disable-debug-info Gerd Hoffmann
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 5/6] save config.log Gerd Hoffmann
2013-02-01 14:02 ` [Qemu-devel] [buildbot patch 6/6] add log tail to failure reports 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=1359727345-10477-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=berendt@b1-systems.de \
--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).