Bug 1093633 - libvirt-glib-0.1.8: tests fail with /bin/sh: ../tap-driver.sh: No such file or directory
Summary: libvirt-glib-0.1.8: tests fail with /bin/sh: ../tap-driver.sh: No such file o...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt-glib
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-02 09:09 UTC by Pacho Ramos
Modified: 2016-03-23 19:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 19:58:50 UTC
Embargoed:

Attachments (Terms of Use)
build.log (547.68 KB, text/x-log)
2014-05-02 09:09 UTC, Pacho Ramos 		no flags Details
View All

Description Pacho Ramos 2014-05-02 09:09:48 UTC 
Created attachment 891751 [details]
build.log

We get:
make  check-TESTS
make[3]: Entering directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
make[4]: Entering directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
/bin/sh: ../tap-driver.sh: No such file or directory
make[4]: *** [test-gconfig.log] Error 127
make[4]: Leaving directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/var/tmp/portage/app-emulation/libvirt-glib-0.1.8/work/libvirt-glib-0.1.8/tests'
make: *** [check-recursive] Error 1
Comment 1 Cole Robinson 2016-03-23 19:58:50 UTC 
Sorry this never received a response. I don't see this issue with libvirt-glib v0.2.3 so I suspect it's fixed. If you still have issues with this with the latest release, I suggest mailing libvir-list instead
Note You need to log in before you can comment on or make changes to this bug.