[libvirt] libvirt-1.0 fails virdrivermoduletest
I've a stable Gentoo Linux, the build log is attached. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
On 11/11/2012 10:25 AM, Toralf Förster wrote:
I've a stable Gentoo Linux, the build log is attached.
It's hard to say from the log, but you can check yourselves what the problem is by running the particular test like this: VIR_TEST_DEBUG=1 ./virdrivermoduletest in the tests/ directory after compiling the source. That should give you an idea where the problem might be. Martin
On 11/19/2012 03:14 PM, Martin Kletzander wrote:
On 11/11/2012 10:25 AM, Toralf Förster wrote:
I've a stable Gentoo Linux, the build log is attached.
It's hard to say from the log, but you can check yourselves what the problem is by running the particular test like this:
VIR_TEST_DEBUG=1 ./virdrivermoduletest
in the tests/ directory after compiling the source. That should give you an idea where the problem might be.
Martin
AH thx, I get : n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virdrivermoduletest TEST: virdrivermoduletest 1) Test driver "storage" ... OK 2) Test driver "nodedev" ... OK 3) Test driver "secret" ... OK 4) Test driver "nwfilter" ... OK 5) Test driver "interface" ... OK 6) Test driver "qemu" ... FAILED 7) Test driver "lxc" ... FAILED 8) Test driver "uml" ... OK and n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virnetsockettest TEST: virnetsockettest 1) Socket TCP/IPv4 Accept ... libvir: XML-RPC error : End of file while reading data: Input/output error OK 2) Socket UNIX Accept ... libvir: XML-RPC error : Cannot write data: Broken pipe OK 3) Socket UNIX Addrs ... OK 4) Socket External Command /dev/zero ... OK 5) Socket External Command /dev/does-not-exist ... libvir: XML-RPC error : End of file while reading data: /bin/cat: /dev/does-not-exist: No such file or directory: Input/output error OK 6) SSH test 1 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname somehost: Name or service not known: Input/output error FAILED 7) SSH test 2 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname somehost: Name or service not known: Input/output error FAILED 8) SSH test 3 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname somehost: Name or service not known: Input/output error FAILED 9) SSH test 4 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname nosuchhost: Name or service not known: Input/output error OK 10) SSH test 5 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname crashyhost: Name or service not known: Input/output error FAILED 11) SSH test 6 ... libvir: XML-RPC error : End of file while reading data: Warning: Identity file /root/.ssh/example_key not accessible: No such file or directory. socket: Address family not supported by protocol ssh: connect to host example.com port 22: Address family not supported by protocol: Input/output error FAILED 12) SSH test 7 ... libvir: XML-RPC error : End of file while reading data: ssh: Could not resolve hostname somehost: Name or service not known: Input/output error FAILED hmm -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
On 11/20/12 20:36, Toralf Förster wrote:
n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virdrivermoduletest TEST: virdrivermoduletest 1) Test driver "storage" ... OK 2) Test driver "nodedev" ... OK 3) Test driver "secret" ... OK 4) Test driver "nwfilter" ... OK 5) Test driver "interface" ... OK 6) Test driver "qemu" ... FAILED 7) Test driver "lxc" ... FAILED 8) Test driver "uml" ... OK
The "qemu" and "lxc" driver tests depend on the "network" driver, which is missing. Enabling the virt-network USE flag should fix the tests and allow you to configure the network with libvirt. Jan
On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
On 11/20/12 20:36, Toralf Förster wrote:
n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virdrivermoduletest TEST: virdrivermoduletest 1) Test driver "storage" ... OK 2) Test driver "nodedev" ... OK 3) Test driver "secret" ... OK 4) Test driver "nwfilter" ... OK 5) Test driver "interface" ... OK 6) Test driver "qemu" ... FAILED 7) Test driver "lxc" ... FAILED 8) Test driver "uml" ... OK
The "qemu" and "lxc" driver tests depend on the "network" driver, which is missing. Enabling the virt-network USE flag should fix the tests and allow you to configure the network with libvirt.
Hmm, if we allow the possibility of biulding without the network driver, then we should make sure the tests pass. I'm curious as to what the actual failure is there. 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 :|
On 11/21/12 10:06, Daniel P. Berrange wrote:
On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
On 11/20/12 20:36, Toralf Förster wrote:
n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virdrivermoduletest TEST: virdrivermoduletest 1) Test driver "storage" ... OK 2) Test driver "nodedev" ... OK 3) Test driver "secret" ... OK 4) Test driver "nwfilter" ... OK 5) Test driver "interface" ... OK 6) Test driver "qemu" ... FAILED 7) Test driver "lxc" ... FAILED 8) Test driver "uml" ... OK
The "qemu" and "lxc" driver tests depend on the "network" driver, which is missing. Enabling the virt-network USE flag should fix the tests and allow you to configure the network with libvirt.
Hmm, if we allow the possibility of biulding without the network driver, then we should make sure the tests pass. I'm curious as to what the actual failure is there.
Daniel
The failure is virdrivermoduletest not being able to load the "network" module, which it has listed as a dependency for "qemu" and "lxc". Removing this dependency fixes the test for me. [1] virnetsockettest passes in make check but fails when run as ./virnetsockettest because it uses the dummy ssh in tests/ in the first case and the system-wide ssh in the other one. It should work as: VIR_TESTS_DEBUG=1 PATH=.:$PATH ./virnetsockettest We could also suppress the "statement with no effect" warning for no-op functions from network/bridge_driver.h to make build with -Werror possible. Jan [1] diff --git a/tests/virdrivermoduletest.c b/tests/virdrivermoduletest.c index 9c14e79..447e18e 100644 --- a/tests/virdrivermoduletest.c +++ b/tests/virdrivermoduletest.c @@ -83,10 +83,10 @@ mymain(void) TEST("interface", NULL); #endif #ifdef WITH_QEMU - TEST("qemu", "network"); + TEST("qemu", NULL); #endif #ifdef WITH_LXC - TEST("lxc", "network"); + TEST("lxc", NULL); #endif #ifdef WITH_UML TEST("uml", NULL);
On Wed, Nov 21, 2012 at 11:56:54AM +0100, Ján Tomko wrote:
On 11/21/12 10:06, Daniel P. Berrange wrote:
On Wed, Nov 21, 2012 at 09:22:25AM +0100, Ján Tomko wrote:
On 11/20/12 20:36, Toralf Förster wrote:
n22 /var/tmp/portage/app-emulation/libvirt-1.0.0/work/libvirt-1.0.0/tests # VIR_TEST_DEBUG=1 ./virdrivermoduletest TEST: virdrivermoduletest 1) Test driver "storage" ... OK 2) Test driver "nodedev" ... OK 3) Test driver "secret" ... OK 4) Test driver "nwfilter" ... OK 5) Test driver "interface" ... OK 6) Test driver "qemu" ... FAILED 7) Test driver "lxc" ... FAILED 8) Test driver "uml" ... OK
The "qemu" and "lxc" driver tests depend on the "network" driver, which is missing. Enabling the virt-network USE flag should fix the tests and allow you to configure the network with libvirt.
Hmm, if we allow the possibility of biulding without the network driver, then we should make sure the tests pass. I'm curious as to what the actual failure is there.
Daniel
The failure is virdrivermoduletest not being able to load the "network" module, which it has listed as a dependency for "qemu" and "lxc". Removing this dependency fixes the test for me. [1]
virnetsockettest passes in make check but fails when run as ./virnetsockettest because it uses the dummy ssh in tests/ in the first case and the system-wide ssh in the other one. It should work as: VIR_TESTS_DEBUG=1 PATH=.:$PATH ./virnetsockettest
Yep, that's a false failure.
We could also suppress the "statement with no effect" warning for no-op functions from network/bridge_driver.h to make build with -Werror possible.
Yep, that should be done. We should be warning-free in all configurations
diff --git a/tests/virdrivermoduletest.c b/tests/virdrivermoduletest.c index 9c14e79..447e18e 100644 --- a/tests/virdrivermoduletest.c +++ b/tests/virdrivermoduletest.c @@ -83,10 +83,10 @@ mymain(void) TEST("interface", NULL); #endif #ifdef WITH_QEMU - TEST("qemu", "network"); + TEST("qemu", NULL); #endif #ifdef WITH_LXC - TEST("lxc", "network"); + TEST("lxc", NULL); #endif #ifdef WITH_UML TEST("uml", NULL);
If you make that change conditional on #ifdef WITH_NETWORK, then we could apply it 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 :|
participants (4)
-
Daniel P. Berrange -
Ján Tomko -
Martin Kletzander -
Toralf Förster