Source: ruby-backports Version: 3.6.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 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): > /usr/lib/ruby/vendor_ruby/rake/testtask.rb:106:in `block (3 levels) in > define': Command failed with status (1): [ruby -I"lib:lib:test" > -I"/usr/lib/ruby/vendor_ruby" > "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" ] > (RuntimeError) > from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:45:in `call' > from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:45:in `sh' > from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:37:in `sh' > from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:84:in `ruby' > from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:37:in `ruby' > from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:102:in `block (2 > levels) in define' > from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:58:in `verbose' > from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:98:in `block in define' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:236:in `call' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:236:in `block in execute' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:231:in `each' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:231:in `execute' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:175:in `block in > invoke_with_call_chain' > from /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:168:in > `invoke_with_call_chain' > from /usr/lib/ruby/vendor_ruby/rake/task.rb:161:in `invoke' > from debian/ruby-tests.rb:5:in `<main>' > ERROR: Test "ruby2.1" failed: The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-backports_3.6.0-1_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. The build was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
