Oddly something seems to have changed since I did the uprev of libvirt to v4.3.0. Previously using the 'run-ptests' script would only run the tests and not attempt to build them first. In preparation for the uprev to v4.5.0 I attempted to run the tests and found that they would fail to run and instead the tests were attempting to be built. I suspect this change is caused by an uprev of autotools and the handling of the 'TESTS' built-in.
To prevent this we are explicitly using the '--with-test-suite' configure option and this return the previously observed behavior, where the tests are simply run and not built. Signed-off-by: Mark Asselstine <[email protected]> --- recipes-extended/libvirt/libvirt_4.3.0.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/recipes-extended/libvirt/libvirt_4.3.0.bb b/recipes-extended/libvirt/libvirt_4.3.0.bb index 194f049..bb4a256 100644 --- a/recipes-extended/libvirt/libvirt_4.3.0.bb +++ b/recipes-extended/libvirt/libvirt_4.3.0.bb @@ -290,6 +290,7 @@ do_install_append() { EXTRA_OECONF += " \ --with-init-script=systemd \ + --with-test-suite \ " EXTRA_OEMAKE = "BUILD_DIR=${B} DEST_DIR=${D}${PTEST_PATH} PTEST_DIR=${PTEST_PATH} SYSTEMD_UNIT_DIR=${systemd_system_unitdir}" -- 2.7.4 -- _______________________________________________ meta-virtualization mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-virtualization
