From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] build bot not updating?
Date: Mon, 15 Jul 2013 12:02:50 +0800 [thread overview]
Message-ID: <20130715040250.GF21224@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20130708053355.GB6938@redhat.com>
On Mon, Jul 08, 2013 at 08:33:55AM +0300, Michael S. Tsirkin wrote:
> I noticed two things with buildbot:
> http://buildbot.b1-systems.de/qemu/builders/pci_x86_64_debian_6_0
>
> 1. up to jun 23 it keept rebuilding same hash - resources could be saved
> by not rebuilding if hash is unchanged
> 2. no builds since jun 23
We need to update the buildbot configuration to use build DTC.
./configure is currently breaking due to lack of a usable DTC.
Stefan
next prev parent reply other threads:[~2013-07-15 4:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 5:33 [Qemu-devel] build bot not updating? Michael S. Tsirkin
2013-07-08 5:35 ` Stefan Weil
2013-07-15 4:02 ` Stefan Hajnoczi [this message]
2013-07-15 8:23 ` Michael S. Tsirkin
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=20130715040250.GF21224@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=mst@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).