On 01/10/2012 11:27 AM, berrange(a)redhat.com wrote:
> Overall status: failed
> Start date: Tue Jan 10 2012
> Start time: 18:05:04 UTC / 13:05:04 EST
> Build counter: 1326218704
> Build timestamp: 1326218704
> URL:
http://builder.virt-tools.org/index.html
>
>
> Module: libvirt
> Status: failed
> URL:
http://builder.virt-tools.org/module-libvirt.html
33) corrupted config audit_logging ... OK
34) corrupted config host_uuid ... OK
35) corrupted config keepalive_interval ... OK
36) corrupted config keepalive_count ... OK
../../tests/daemon-conf: line 102: 7329 Aborted
$abs_top_builddir/daemon/libvirtd --pid-file=pid-file --config=tmp.conf
> log 2>&1
37) valid config file (sleeping 2 seconds) ... FAILED
FAIL: daemon-conf
I wonder if this was just a failure due to heavy load exceeding what is
normally a reasonable timeout value, and if there is any way to make the
test more robust.
This builder is running inside a virtual machine, so it is possible we
might race. I don't have any good suggestions to improve it though.
This test case has always been very unreliable, breaking for no good
reason.
Daniel
--
|: