[DRE-maint] Bug#725547: ruby-hiera: FTBFS: ERROR: Test "ruby1.9.1" failed.

[David Suárez]

Source: ruby-hiera
Version: 1.0.0~rc3-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131006 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):
> 
> Finished in 0.12908 seconds
> 80 examples, 8 failures
> 
> Failed examples:
> 
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should return the answer from the backend
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should retain the datatypes as returned by the backend
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should call to all backends till an answer is found
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should parse the answers based on resolution_type
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should return the default with variables parsed if nothing is found
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle string default data
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle array default data
> rspec /usr/lib/ruby/vendor_ruby/rspec/core/metadata.rb:187 # Hiera::Backend#lookup should correctly handle hash default data
> /usr/bin/ruby1.9.1 -S rspec spec/unit/backend/yaml_backend_spec.rb spec/unit/backend_spec.rb spec/unit/config_spec.rb spec/unit/console_logger_spec.rb spec/unit/hiera_spec.rb --format s --colour --backtrace failed
> ERROR: Test "ruby1.9.1" failed.

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/10/06/ruby-hiera_1.0.0~rc3-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.