[DRE-maint] Bug#869054: ruby-dalli: FTBFS: ERROR: Test "ruby2.3" failed.

[Lucas Nussbaum]

Source: ruby-dalli
Version: 2.7.4-1
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170720 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/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Checking Rubygems dependency resolution on ruby2.3                           │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 -e gem\ \"dalli\"
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake                            │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-dalli/usr/lib/ruby/vendor_ruby:. GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -w -I"test"  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" -v
> /usr/lib/ruby/2.3.0/rubygems/specification.rb:2287:in `raise_if_conflicts': Unable to activate rails-dom-testing-1.0.6, because nokogiri-1.8.0 conflicts with nokogiri (~> 1.6.0) (Gem::ConflictError)
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1408:in `activate'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in activate_dependencies'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `activate_dependencies'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1442:in `block in activate_dependencies'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `activate_dependencies'
> 	from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
> 	from /<<PKGBUILDDIR>>/test/helper.rb:14:in `<top (required)>'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /<<PKGBUILDDIR>>/test/benchmark_test.rb:1:in `<top (required)>'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> 	from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55: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>'
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.3" failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/07/20/ruby-dalli_2.7.4-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.