Source: ruby-listen
Version: 3.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: rel_path = path.relative_path_from(dir).to_s
>
> TypeError:
> no implicit conversion of RSpec::Mocks::InstanceVerifyingDouble into
> String
> # ./lib/listen/adapter/linux.rb:48:in `_process_event'
> # ./lib/listen/adapter/base.rb:42:in `block (2 levels) in configure'
> # ./spec/lib/listen/adapter/linux_spec.rb:99:in `block (5 levels) in
> <top (required)>'
> # ./spec/lib/listen/adapter/linux_spec.rb:98:in `each'
> # ./spec/lib/listen/adapter/linux_spec.rb:98:in `block (4 levels) in
> <top (required)>'
> # ./spec/lib/listen/adapter/linux_spec.rb:118:in `block (3 levels) in
> <top (required)>'
>
> Finished in 2 minutes 17.5 seconds (files took 0.25371 seconds to load)
> 316 examples, 3 failures, 1 pending
>
> Failed examples:
>
> rspec ./spec/lib/listen/adapter/linux_spec.rb:121 # Listen::Adapter::Linux
> _callback recognizes moved_from as moved_from
> rspec ./spec/lib/listen/adapter/linux_spec.rb:111 # Listen::Adapter::Linux
> _callback recognizes close_write as modify
> rspec ./spec/lib/listen/adapter/linux_spec.rb:116 # Listen::Adapter::Linux
> _callback recognizes moved_to as moved_to
>
> Randomized with seed 44939
>
> /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 --exclude-pattern
> ./spec/lib/listen/adapter/\{darwin,windows\}_spec.rb --format documentation
> failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2020/02/22/ruby-listen_3.1.5-1_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.
