Source: ruby-vips
Version: 2.0.17-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>      Failure/Error: expect(image.avg).to be_within(0.001).of(109.789)
>        expected 109.41407425505706 to be within 0.001 of 109.789
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib/rspec/support.rb:102:in
>  `block in <module:Support>'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib/rspec/support.rb:111:in
>  `notify_failure'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/fail_with.rb:35:in
>  `fail_with'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:40:in
>  `handle_failure'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:56:in
>  `block in handle_matcher'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:27:in
>  `with_matcher'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/handler.rb:48:in
>  `handle_matcher'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.10.1/lib/rspec/expectations/expectation_target.rb:65:in
>  `to'
>      # ./spec/connection_spec.rb:165:in `block (2 levels) in <top (required)>'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in
>  `instance_exec'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:262:in
>  `block in run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in
>  `block in with_around_and_singleton_context_hooks'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in
>  `block in with_around_example_hooks'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in
>  `block in run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:624:in
>  `run_around_example_hooks_for'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/hooks.rb:486:in
>  `run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:465:in
>  `with_around_example_hooks'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:508:in
>  `with_around_and_singleton_context_hooks'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example.rb:259:in
>  `run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:644:in
>  `block in run_examples'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in
>  `map'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:640:in
>  `run_examples'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/example_group.rb:606:in
>  `run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in
>  `block (3 levels) in run_specs'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in
>  `map'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:121:in
>  `block (2 levels) in run_specs'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/configuration.rb:2067:in
>  `with_suite_hooks'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:116:in
>  `block in run_specs'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/reporter.rb:74:in
>  `report'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:115:in
>  `run_specs'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:89:in
>  `run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:71:in
>  `run'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib/rspec/core/runner.rb:45:in
>  `invoke'
>      # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec:4:in 
> `<main>'
> 
> Finished in 0.98992 seconds (files took 0.28122 seconds to load)
> 91 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/connection_spec.rb:151 # Vips::SourceCustom can write an image 
> to a user output stream
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --backtrace -r ./spec/spec_helper.rb failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/ruby-vips_2.0.17-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220813&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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.

Reply via email to