[DRE-maint] Bug#954503: ruby-mustache: FTBFS: ERROR: Test "ruby2.7" failed.

[Lucas Nussbaum]

Source: ruby-mustache
Version: 1.0.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rb                              │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-mustache/usr/lib/ruby/vendor_ruby:. GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-mustache/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 ruby2.7 debian/ruby-tests.rb
> Run options: --seed 47874
> 
> # Running:
> 
> ................FFF............................................................................
> 
> Finished in 0.041855s, 2269.7384 runs/s, 2986.4979 assertions/s.
> 
>   1) Failure:
> AutoloadingTest#test_autoload [/<<PKGBUILDDIR>>/test/autoloading_test.rb:12]:
> Expected: Comments
>   Actual: nil
> 
>   2) Failure:
> AutoloadingTest#test_autoload_lowercase [/<<PKGBUILDDIR>>/test/autoloading_test.rb:17]:
> Expected: Comments
>   Actual: nil
> 
>   3) Failure:
> AutoloadingTest#test_folder_autoload [/<<PKGBUILDDIR>>/test/autoloading_test.rb:40]:
> Expected: TestViews::Namespaced
>   Actual: nil
> 
> 95 runs, 125 assertions, 3 failures, 0 errors, 0 skips
> ERROR: Test "ruby2.7" failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/ruby-mustache_1.0.2-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.