From: Dustin Kirkland <kirkland@canonical.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org, libvir-list@redhat.com
Cc: Ubuntu Developers <ubuntu-devel@lists.ubuntu.com>
Subject: [Qemu-devel] daily builds of pristine upstream sources for qemu, qemu-kvm, and libvirt
Date: Tue, 7 Jul 2009 16:30:44 -0500 [thread overview]
Message-ID: <d9c105ea0907071430g58ac09f0nb8296191132703d2@mail.gmail.com> (raw)
Howdy, developers of qemu, qemu-kvm, and libvirt. I periodically see
bug reports on these lists from users of Ubuntu packages of these
projects.
Since these users are often running some version of the project older
than the current development branch, it's more interesting to know if
the user can reproduce the bug on the latest development sources.
I have constructed some automation that builds Debian/Ubuntu binaries
for amd64, i386, and lpia platforms directly from your master git
repositories every day at 11:00 UTC, and publishes them in a special,
opt-in repository. These daily builds also drop any specific patches
we may be carrying, in order to minimize the delta between the
binaries built and your upstream sources.
* https://launchpad.net/~ubuntu-virt/+archive/virt-daily-upstream
In the event that an Ubuntu user reports a problem, and there's an
interest in trying to reproduce the problem against the tip of the
development branch, we can point them at this resource for testing
purposes.
Additionally, this tool also has the ability to expose build
breakages. For example (let's not debug this in this thread), at the
moment, qemu's build is broken, somewhere near:
....
LINK cris-softmmu/qemu-system-cris
../libqemu_common.a(esdaudio.o): In function `qesd_run_in':
/build/buildd/qemu-0.10.50.20090707062004/audio/esdaudio.c:400:
undefined reference to `audio_pt_lock'
....
Launchpad publishes the full build logs available for each
architecture at the link above. For the above example, the specific
build log is:
* http://launchpadlibrarian.net/28761559/buildlog_ubuntu-karmic-amd64.qemu_0.10.50.20090707062004-0daily1_FAILEDTOBUILD.txt.gz
If anyone has suggestions as to the utility of this resource, I would
appreciate constructive feedback.
Cheers,
--
:-Dustin
reply other threads:[~2009-07-07 21:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d9c105ea0907071430g58ac09f0nb8296191132703d2@mail.gmail.com \
--to=kirkland@canonical.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ubuntu-devel@lists.ubuntu.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;
as well as URLs for NNTP newsgroup(s).