[DRE-maint] Bug#860696: ruby-spy: FTBFS on i386: ERROR: Test "ruby2.3" failed: SyntaxError: /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|'

[Lucas Nussbaum]

Source: ruby-spy
Version: 0.4.3-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):
> SyntaxError: /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:229: syntax error, unexpected '-', expecting '|'
>       lambda do |*__spy_args_-56954028, &block|
>                               ^
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in `eval'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:227:in `override_method'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:55:in `hook'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:315:in `on'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:188:in `create_and_hook_spy'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:22:in `block in on'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:21:in `map'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:21:in `on'
>     /<<PKGBUILDDIR>>/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy.rb:144:in `mock_all'
>     /<<PKGBUILDDIR>>/test/integration/test_mocking.rb:22:in `test_spy_mock_all'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
>     /usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:799:in `run_one_method'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:322:in `run_one_method'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block (2 levels) in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `each'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:309:in `block in run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:348:in `on_signal'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:335:in `with_info_handler'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:308:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `block in __run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `map'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:158:in `__run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:135:in `run'
>     /usr/lib/ruby/vendor_ruby/minitest.rb:62:in `block in autorun'
> 
> 64 runs, 32 assertions, 0 failures, 33 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -I"test"  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/integration/test_api.rb" "test/integration/test_constant_spying.rb" "test/integration/test_instance_method.rb" "test/integration/test_mocking.rb" "test/integration/test_subroutine_spying.rb" "test/spy/test_mock.rb" "test/spy/test_subroutine.rb" "test/test_helper.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/04/18/ruby-spy_0.4.3-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.