Source: ruby-integration
Version: 0.1.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ..FFFFWARNING: Using the `raise_error` matcher without providing a specific
> error or message risks false positives, since `raise_error` will match when
> Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially
> allowing the expectation to pass without even executing the method you are
> intending to call. Actual error raised was #<RuntimeError: Ruby methods
> doesn't support infinity bounds>. Instead consider providing a specific error
> class or message. This message can be suppressed by setting:
> `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`.
> Called from /<<PKGBUILDDIR>>/spec/integration_spec.rb:61:in `block (2 levels)
> in <top (required)>'.
> .
>
> Failures:
>
> 1) Integration should return a correct value for a complex integration with
> gsl methods FIXED
> Expected pending 'GSL not available' to fail. No error was raised.
> # ./spec/integration_spec.rb:19
>
> 2) Integration should return correct integration for infinity bounds FIXED
> Expected pending 'GSL not available' to fail. No error was raised.
> # ./spec/integration_spec.rb:30
>
> 3) Integration should return correct integration for infinity lower bound
> FIXED
> Expected pending 'GSL not available' to fail. No error was raised.
> # ./spec/integration_spec.rb:39
>
> 4) Integration should return correct integration for infinity upper bound
> FIXED
> Expected pending 'GSL not available' to fail. No error was raised.
> # ./spec/integration_spec.rb:49
>
> Deprecation Warnings:
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<<PKGBUILDDIR>>/spec/integration_spec.rb:9:in `block (3 levels) in <top
> (required)>'.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 1 deprecation warning total
>
> Finished in 0.01128 seconds (files took 0.09876 seconds to load)
> 7 examples, 4 failures
>
> Failed examples:
>
> rspec ./spec/integration_spec.rb:19 # Integration should return a correct
> value for a complex integration with gsl methods
> rspec ./spec/integration_spec.rb:30 # Integration should return correct
> integration for infinity bounds
> rspec ./spec/integration_spec.rb:39 # Integration should return correct
> integration for infinity lower bound
> rspec ./spec/integration_spec.rb:49 # Integration should return correct
> integration for infinity upper bound
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/ruby-integration_0.1.0-1.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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
