[DRE-maint] Bug#860651: ruby-awesome-print: FTBFS on i386: ERROR: Test "ruby2.3" failed: Failure/Error: expect(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to eq(str)

[Lucas Nussbaum]

Source: ruby-awesome-print
Version: 1.6.1-2
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(out.gsub(/0x([a-f\d]+)/, "0x01234567")).to eq(str)
> 
>        expected: "#<Hello:0x01234567\n    @doo = 1,\n    @dooby = 2,\n    @scooby = 3,\n    attr_accessor :dabra = 3,\n    attr_reader :abra = 1,\n    attr_writer :ca = 2\n>"
>             got: "#<Hello:0x..f88dc89c\n    @doo = 1,\n    @dooby = 2,\n    @scooby = 3,\n    attr_accessor :dabra = 3,\n    attr_reader :abra = 1,\n    attr_writer :ca = 2\n>"
> 
>        (compared using ==)
> 
>        Diff:
>        @@ -1,4 +1,4 @@
>        -#<Hello:0x01234567
>        +#<Hello:0x..f88dc89c
>             @doo = 1,
>             @dooby = 2,
>             @scooby = 3,
>      # ./spec/objects_spec.rb:81:in `block (3 levels) in <top (required)>'
> 
> Finished in 0.29284 seconds (files took 0.28149 seconds to load)
> 135 examples, 3 failures
> 
> Failed examples:
> 
> rspec ./spec/objects_spec.rb:13 # Objects Formatting an object attributes
> rspec ./spec/objects_spec.rb:37 # Objects Formatting an object instance variables
> rspec ./spec/objects_spec.rb:57 # Objects Formatting an object attributes and instance variables
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

The full build log is available from:
   http://aws-logs.debian.net/2017/04/18/ruby-awesome-print_1.6.1-2_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.