[DRE-maint] Bug#860693: ruby-rspec: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to match(/\A#<BasicObject:0x[0-9a-f]{14}>\z/)

[Lucas Nussbaum]

Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170418-i386 qa-ftbfs
Justification: FTBFS in stretch on i386

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on i386.

Relevant part (hopefully):
>      Failure/Error: expect(output).to match(/\A#<BasicObject:0x[0-9a-f]{14}>\z/)
> 
>        expected "#<BasicObject:0x..fffff90f3710>" to match /\A#<BasicObject:0x[0-9a-f]{14}>\z/
>        Diff:
>        @@ -1,2 +1,2 @@
>        -/\A#<BasicObject:0x[0-9a-f]{14}>\z/
>        +"#<BasicObject:0x..fffff90f3710>"
>      # ./spec/rspec/support/object_formatter_spec.rb:191:in `block (3 levels) in <module:Support>'
>      # debian/ruby-tests.rb:30:in `block (3 levels) in <main>'
>      # debian/ruby-tests.rb:24:in `chdir'
>      # debian/ruby-tests.rb:24:in `block (2 levels) in <main>'
>      # debian/ruby-tests.rb:23:in `fork'
>      # debian/ruby-tests.rb:23:in `block in <main>'
>      # debian/ruby-tests.rb:22:in `each'
>      # debian/ruby-tests.rb:22:in `<main>'
> 
> Finished in 0.98638 seconds (files took 0.49044 seconds to load)
> 458 examples, 1 failure, 2 pending
> 
> Failed examples:
> 
> rspec ./spec/rspec/support/object_formatter_spec.rb:190 # RSpec::Support::ObjectFormatter.format with an object that does not respond to #inspect such as BasicObject produces an output emulating MRI's #inspect-like output generated by C implementation
> 
> Randomized with seed 4285
> 
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/ruby-rspec_3.5.0c3e0m0s0-1_testing-i386.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.