[DRE-maint] Bug#952086: ruby-highline: FTBFS: ERROR: Test "ruby2.7" failed: Error: test_Highline_String_is_yaml_serializable(TestStringExtension): RuntimeError: CRITICAL: RUBYGEMS_ACTIVATION_MONITOR.owned?: before false -> after true
Lucas Nussbaum
lucas at debian.org
Sun Feb 23 07:44:57 GMT 2020
Source: ruby-highline
Version: 1.7.8-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Error: test_Highline_String_is_yaml_serializable(TestStringExtension): RuntimeError: CRITICAL: RUBYGEMS_ACTIVATION_MONITOR.owned?: before false -> after true
> E
> ===============================================================================
> Error: test_Highline_String_is_yaml_serializable(TestStringExtension): SystemStackError: stack level too deep
>
> Finished in 0.298043755 seconds.
> -------------------------------------------------------------------------------
> 88 tests, 321 assertions, 0 failures, 2 errors, 0 pendings, 0 omissions, 0 notifications
> 100% passed
> -------------------------------------------------------------------------------
> 295.26 tests/s, 1077.02 assertions/s/<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `raise': stack level too deep (SystemStackError)
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `method_missing'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `initialize'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `exception'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `raise'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `method_missing'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `initialize'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `exception'
> from /<<PKGBUILDDIR>>/debian/ruby-highline/usr/lib/ruby/vendor_ruby/highline/string_extensions.rb:97:in `raise'
> ... 8887 levels...
> from /usr/share/rubygems-integration/all/gems/test-unit-3.3.4/lib/test/unit/autorunner.rb:495:in `change_work_directory'
> from /usr/share/rubygems-integration/all/gems/test-unit-3.3.4/lib/test/unit/autorunner.rb:438:in `run'
> from /usr/share/rubygems-integration/all/gems/test-unit-3.3.4/lib/test/unit/autorunner.rb:66:in `run'
> from /usr/share/rubygems-integration/all/gems/test-unit-3.3.4/lib/test/unit.rb:511:in `block (2 levels) in <top (required)>'
>
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-highline_1.7.8-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.
More information about the Pkg-ruby-extras-maintainers
mailing list