Your message dated Sun, 12 Apr 2020 15:55:19 +0530
with message-id <7m7o8q.axi5t14j9u...@onenetbeyond.org>
and subject line fixed in last upload
has caused the Debian Bug report #955678,
regarding ruby-mail-room: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
expect(redis.client.instance_variable_get(:@connector)).to be_a
Redis::Client::Connector::Sentinel
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.)
--
955678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-mail-room
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
> expect(redis.client.instance_variable_get(:@connector)).to be_a
> Redis::Client::Connector::Sentinel
>
> TypeError:
> no implicit conversion of Symbol into Integer
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:346:in
> `establish_connection'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:106:in
> `block in connect'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:306:in
> `with_reconnect'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:105:in
> `connect'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:381:in
> `ensure_connected'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:231:in
> `block in process'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:319:in
> `logging'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:230:in
> `process'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis/client.rb:125:in
> `call'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:222:in
> `block in client'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:52:in
> `block in synchronize'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:52:in
> `synchronize'
> #
> /usr/share/rubygems-integration/all/gems/redis-4.1.2/lib/redis.rb:221:in
> `client'
> # ./spec/lib/delivery/sidekiq_spec.rb:68:in `block (4 levels) in <top
> (required)>'
>
> Finished in 2.11 seconds (files took 0.69204 seconds to load)
> 63 examples, 4 failures
>
> Failed examples:
>
> rspec ./spec/lib/arbitration/redis_spec.rb:94 # MailRoom::Arbitration::Redis
> redis client connection params when only url is present client has same
> specified url
> rspec ./spec/lib/arbitration/redis_spec.rb:138 # MailRoom::Arbitration::Redis
> redis client connection params when sentinel is present client has same
> specified sentinel params
> rspec ./spec/lib/delivery/sidekiq_spec.rb:22 #
> MailRoom::Delivery::Sidekiq#options when only redis_url is specified client
> has same specified redis_url
> rspec ./spec/lib/delivery/sidekiq_spec.rb:67 #
> MailRoom::Delivery::Sidekiq#options when sentinel is specified client has
> same specified sentinel params
>
> Randomized with seed 21503
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> pkill redis-server || true
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/04/02/ruby-mail-room_0.10.0-2_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 ---
fixed -1 955678 0.10.0+really0.0.3-1
thanks
--- End Message ---
