On 01/10/2012 11:27 AM, berrange@xxxxxxxxxx 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. -- Eric Blake eblake@xxxxxxxxxx +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list