From: "Daniel P. Berrange" <berrange@redhat.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: libvir-list@redhat.com, Ian Jackson <ian.jackson@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Daniel Veillard <veillard@redhat.com>
Subject: Re: [libvirt] libvirt / libxl testing emails
Date: Tue, 3 Jun 2014 15:30:46 +0100 [thread overview]
Message-ID: <20140603143046.GX4207@redhat.com> (raw)
In-Reply-To: <538DD8D1.8010304@eu.citrix.com>
On Tue, Jun 03, 2014 at 03:16:49PM +0100, George Dunlap wrote:
> Ian / Ian,
>
> Daniel V. was lurking on a recent CentOS Virt SIG IRC meetings, and asked
> about testing the libvirt git repo against libxl. I mentioned that we
> already had some basic tests to do that, and he asked whether it would make
> sense to have the push gate e-mail the libvirt list.
>
> I have no idea how the libvirt people feel about that, so I'll let DV make
> his case, and also let he Ians give their opinions.
I guess from my POV the answer probably hinges on the reliability of the
test harness. If it has a very low false failure rate, then it'd be ok
to send it to this list. Conversely if there's a non-trivial false failure
rate it'd be better to have it go to an individual who filters it and just
forwards the real failures to the list.
An alternative idea would be for us to setup a new 'libvirt-testing'
mailing list, exclusively for spamming by CI systems, that people could
opt-in to subscribing to.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2014-06-03 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 14:16 libvirt / libxl testing emails George Dunlap
2014-06-03 14:30 ` Daniel P. Berrange [this message]
2014-06-03 14:37 ` [libvirt] " George Dunlap
[not found] ` <538DDDA4.20302@eu.citrix.com>
2014-06-03 14:45 ` Ian Campbell
2014-06-03 16:00 ` Daniel Veillard
[not found] ` <20140603160041.GC14854@redhat.com>
2014-06-06 8:25 ` Ian Campbell
[not found] ` <1402043146.29759.11.camel@kazak.uk.xensource.com>
2014-06-06 9:32 ` Daniel Veillard
2014-06-06 9:47 ` Ian Campbell
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=20140603143046.GX4207@redhat.com \
--to=berrange@redhat.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=libvir-list@redhat.com \
--cc=veillard@redhat.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.