[DRE-maint] Bug#844925: ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.3" failed: ArgumentError: argument out of range

Lucas Nussbaum lucas at debian.org
Sat Nov 19 07:05:37 UTC 2016


Source: ruby-sidekiq-cron
Version: 0.4.2-5
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ArgumentError: argument out of range
>     /<<PKGBUILDDIR>>/test/unit/poller_test.rb:83:in `initialize'
>     /<<PKGBUILDDIR>>/test/unit/poller_test.rb:83:in `new'
>     /<<PKGBUILDDIR>>/test/unit/poller_test.rb:83:in `block (2 levels) in <top (required)>'
>     /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'
> 
> 83 runs, 155 assertions, 0 failures, 4 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -I"lib:test"  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/unit/job_test.rb" "test/unit/poller_test.rb" "test/unit/web_extesion_test.rb" ]
> 
> Tasks: TOP => test
> (See full trace by running task with --trace)
> + cleanup
> + kill -9 114156
> rake aborted!
> Command failed with status (1): [./debian/start-redis-server.sh ruby2.3 -S ...]
> /<<PKGBUILDDIR>>/debian/ruby-tests.rake:5:in `block in <top (required)>'
> 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/2016/11/18/ruby-sidekiq-cron_0.4.2-5_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