Source: ruby-libvirt Version: 0.5.1-2 Severity: serious Tags: jessie sid User: [email protected] Usertags: qa-ftbfs-20140208 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory `/«PKGBUILDDIR»/ext/libvirt' > compiling storage.c > compiling nodedevice.c > compiling domain.c > In file included from domain.c:26:0: > /usr/include/ruby-1.9.1/ruby/backward/st.h:2:2: warning: #warning use > "ruby/st.h" instead of bare "st.h" [-Wcpp] > #warning use "ruby/st.h" instead of bare "st.h" > ^ > compiling connect.c > compiling secret.c > compiling _libvirt.c > compiling nwfilter.c > compiling common.c > In file included from common.c:27:0: > /usr/include/ruby-1.9.1/ruby/backward/st.h:2:2: warning: #warning use > "ruby/st.h" instead of bare "st.h" [-Wcpp] > #warning use "ruby/st.h" instead of bare "st.h" > ^ > compiling stream.c > compiling interface.c > compiling network.c > linking shared-object _libvirt.so > make[2]: Leaving directory `/«PKGBUILDDIR»/ext/libvirt' > /«PKGBUILDDIR»/tests/test_open.rb:27:in `<top (required)>': undefined method > `close' for 1:Fixnum (NoMethodError) > from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' > from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' > from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in > <main>' > from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select' > from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `<main>' > OK: nodedevice.name too many args threw ArgumentError > OK: nodedevice.name no args succeeded > OK: nodedevice.parent too many args threw ArgumentError > OK: nodedevice.parent no args succeeded > OK: nodedevice.num_of_caps too many args threw ArgumentError > OK: nodedevice.num_of_caps no args succeeded > OK: nodedevice.list_caps too many args threw ArgumentError > OK: nodedevice.list_caps no args succeeded > OK: nodedevice.xml_desc too many args threw ArgumentError > OK: nodedevice.xml_desc invalid arg type threw TypeError > OK: nodedevice.xml_desc no args succeeded > OK: nodedevice.detach too many args threw ArgumentError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.detach invalid arg type threw TypeError > OK: nodedevice.reattach too many args threw ArgumentError > OK: nodedevice.reset too many args threw ArgumentError > OK: nodedevice.destroy too many args threw ArgumentError > OK: nodedevice.free too many args threw ArgumentError > OK: nodedevice.free no args succeeded > Successfully finished 23 tests, failed 0 tests, skipped 0 tests > OK: Libvirt.version too many args threw ArgumentError > OK: Libvirt.version invalid arg type threw TypeError > OK: Libvirt.version no args succeeded > OK: Libvirt.version nil arg succeeded > OK: Libvirt.version Test arg succeeded > OK: Libvirt.open too many args threw ArgumentError > OK: Libvirt.open invalid driver threw Libvirt::ConnectionError > FAIL: Libvirt.open no args expected to succeed, threw > Libvirt::ConnectionError: Call to virConnectOpen failed: Failed to connect > socket to '/sbuild-nonexistent/.cache/libvirt/libvirt-sock': No such file or > directory > rake aborted! > Command failed with status (1): [ruby -I"lib:ext/libvirt" > -I"/usr/lib/ruby/vendor_ruby" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" > "tests/test_nodedevice.rb" "tests/test_open.rb" "tests/test_stream.rb" ] > > Tasks: TOP => test > (See full trace by running task with --trace) > make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/02/08/ruby-libvirt_0.5.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
