public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: Juan Quintela <quintela@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Christian Berendt <berendt@b1-systems.de>,
	Alexander Graf <agraf@suse.de>
Subject: Re: QEMU buildbot maintenance state
Date: Mon, 28 Jan 2013 16:10:23 +0100	[thread overview]
Message-ID: <510694DF.1090203@suse.de> (raw)
In-Reply-To: <26158107.iff9SemuRB@marvin.site>

Hi Daniel,

Am 28.01.2013 15:29, schrieb Daniel Gollub:
> thanks for bringing this topic up.
> 
> January was quite busy month for me so far I could only handle minor changes 
> on the buildbot. I hesitate to make larger changes to avoid I break other 
> stuff. So I just queued them up once I have more time (beginning in February 
> or so)
[snip]

Some kind of reply indicating so would've been nice, you were already
CC'ed last year a few times. ;)

Anyway, my point is that we are approaching Hard Freeze and seeing
weekly pulls with recurring breakages on one or another platform (pci on
ppc, s390x on mingw32). Some people have been assuming that if they
don't get mails from the build bots then their tree is okay to merge.

Our shortened release cycle leads to two weeks of Soft Freeze where
everyone pushes their queues before Feb 1 and most breakages occur.
During Hard Freeze we can still try to fix anything the bots report, but
catching errors before they land in master would be better:

At QEMU Summit Anthony requested that each submaintainer's tree be added
to the buildbot system; if there are as you now indicate build power
shortages, I suggest you specify what exactly is needed, maybe someone
in the community can help out. To me it was not clear at least. The
revived ppc slave is hopefully not running into a bottleneck yet. :)

I'll take a look at the config later.

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-01-28 15:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 10:59 KVM call agenda for 2013-01-29 Juan Quintela
2013-01-28 13:02 ` [Qemu-devel] " Andreas Färber
2013-01-28 14:29   ` QEMU buildbot maintenance state (was: Re: KVM call agenda for 2013-01-29) Daniel Gollub
2013-01-28 15:10     ` Andreas Färber [this message]
2013-01-29 12:33     ` [Qemu-devel] " Stefan Hajnoczi
2013-01-30  9:31       ` [Qemu-devel] QEMU buildbot maintenance state Gerd Hoffmann
2013-01-30 14:41         ` Anthony Liguori
2013-01-31 12:54         ` Stefan Hajnoczi
2013-01-31 12:58           ` Christian Berendt
2013-02-01 17:22             ` Christian Berendt
2013-01-31 12:55         ` Stefan Hajnoczi
2013-01-29 15:04     ` Christian Berendt
2013-01-30  9:39       ` Stefan Hajnoczi
2013-01-28 13:29 ` KVM call agenda for 2013-01-29 Stefan Hajnoczi
2013-01-28 14:14 ` Anthony Liguori
2013-01-29  8:49   ` Alexander Graf
2013-01-29 10:01     ` Peter Maydell
2013-01-29 13:02 ` Andreas Färber

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=510694DF.1090203@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=berendt@b1-systems.de \
    --cc=gollub@b1-systems.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    /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