Your message dated Sun, 27 Nov 2016 07:03:22 +0000
with message-id <e1catug-0005zw...@fasolo.debian.org>
and subject line Bug#844925: fixed in ruby-sidekiq-cron 0.4.2-6
has caused the Debian Bug report #844925,
regarding ruby-sidekiq-cron: FTBFS: ERROR: Test "ruby2.3" failed:
ArgumentError: argument out of range
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
844925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sidekiq-cron
Version: 0.4.2-5
Severity: serious
Tags: stretch sid
User: debian...@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.
--- End Message ---
--- Begin Message ---
Source: ruby-sidekiq-cron
Source-Version: 0.4.2-6
We believe that the bug you reported is fixed in the latest version of
ruby-sidekiq-cron, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 844...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pirate Praveen <prav...@debian.org> (supplier of updated ruby-sidekiq-cron
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 27 Nov 2016 11:51:48 +0530
Source: ruby-sidekiq-cron
Binary: ruby-sidekiq-cron
Architecture: source
Version: 0.4.2-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Pirate Praveen <prav...@debian.org>
Description:
ruby-sidekiq-cron - scheduling add-on for Sidekiq
Closes: 844925
Changes:
ruby-sidekiq-cron (0.4.2-6) unstable; urgency=medium
.
* Disable tests that fail when run at specific times (Closes: #844925)
Checksums-Sha1:
12e0e62ce1aa9ad7dd7063de043fe57983fa2e65 2260 ruby-sidekiq-cron_0.4.2-6.dsc
b34cb56696bd71a748db07de6e935da6c3417ef8 4088
ruby-sidekiq-cron_0.4.2-6.debian.tar.xz
Checksums-Sha256:
8b352555e53b5e194a211dbb379fa856c11ee8631ed5ef75e2cd2838c292f765 2260
ruby-sidekiq-cron_0.4.2-6.dsc
0b87782b108ff383b7a60f6d344eb089e4fa88dda8d42c069e4d35581939fe65 4088
ruby-sidekiq-cron_0.4.2-6.debian.tar.xz
Files:
4925872f81dfb48436445186bb753acd 2260 ruby optional
ruby-sidekiq-cron_0.4.2-6.dsc
1ad18544cbeb05fe1b2e3473796d00c5 4088 ruby optional
ruby-sidekiq-cron_0.4.2-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJYOoISAAoJEM4fnGdFEsIqBZ8QAKy/eKTTe09B5ndP/scritpX
gL6MJo77cuaJwZudUvUbbM/x5JdDD6zESk/Clm3VFNhWjeEugi2z6RnsbM8/FyYe
kUi/9mn473nCcFmdyGCShMAb5sOHqsPcvh3/i2EZ+QohZjG2XAqldToCHE+HGAa/
JHGLp+iMaBCADqEiBnXsnlcmxCW2nZM6txNl+e6VIyNy5HFd56YtObIi3+6MOaQ+
pFokVCA71Tc8hKw8v3OzoTpQi2QUvnHlx7tDune/DstUS1ZmeO5HnlHODlFnR/6Y
Q8Phqe43NYQG9gd/tK3GChlTRFLgfOnYlb/32NGsZZrbkDGdvlNOCptvNMmkt3+V
RBY9QyWxsaBzjalWMjISoapYdJw3cILgeVIxkiOzYyNoW6Bm260STlh2N86gs71y
oU1KL9MGwVOJWREyPkWDKIJJyWDG0w+A5cmAuespfCyWTAL86AHIDOC0t506bDpZ
o1ED/8hs0UtqtJZw7c+iM/P+/4UL5SBFB7RG5f2TuQCQI87LaD+DPOddKNSjuU43
TuZ3/aofiAxR1lamR+b4BnpeM9Y2Hgd9XugHT0PISaR2ZVkVfuFPJU8o5dKma9Vf
lLQfPO5Yxwr+p16ONh6w3VCg3BJYJWQrgU30SpQ/fBvRLlw0xSDjaL/EEmgf8KE1
VbjE5yY9uqBt5CII9Wvf
=q2pD
-----END PGP SIGNATURE-----
--- End Message ---
