Your message dated Wed, 01 Dec 2021 03:41:48 +0100
with message-id <c3f02139debb7ceb18f1cff39594ba0074d056bc.ca...@debian.org>
and subject line Not reproducible anymore
has caused the Debian Bug report #998504,
regarding ruby-integration: FTBFS: ERROR: Test "ruby3.0" failed
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.)
--
998504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.
--- End Message ---
--- Begin Message ---
Hi,
this issue is not reproducible anymore. The package builds fine, and it tests
successfully in both unstable and testing. Maybe the problem was caused by
ruby-gsl before the Ruby 3.0 fix was applied (#996237).
Regards, Daniel
--
Regards,
Daniel Leidert <dleid...@debian.org> | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
signature.asc
Description: This is a digitally signed message part
--- End Message ---
