Source: ruby-factory-bot Version: 6.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-factory-bot with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> expected NoMethodError with "undefined method
> 'static_attributes_are_gone' in 'broken' factory\nDid you mean?
> 'static_attributes_are_gone { \"true\" }'\n", got #<NoMethodError: undefined
> method 'static_attributes_are_gone' in 'broken' factory
> Did you mean? 'static_attributes_are_gone { "true" }'
>
>
> raise NoMethodError.new(<<~MSG)
> ^^^^^> with backtrace:
> # ./lib/factory_bot/definition_proxy.rb:99:in `method_missing'
> # ./spec/factory_bot/definition_proxy_spec.rb:69:in `block (3
> levels) in <top (required)>'
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2
> levels) in <top (required)>'
> # ./spec/factory_bot/definition_proxy_spec.rb:71:in `block (2 levels) in
> <top (required)>'
>
> Finished in 0.429 seconds (files took 0.32709 seconds to load)
> 290 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/factory_bot/definition_proxy_spec.rb:66 #
> FactoryBot::DefinitionProxy#method_missing raises a NoMethodError when called
> with a static-attribute-like argument
>
> Randomized with seed 11142
>
> /usr/bin/ruby3.1
> -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,factory_bot/\*\*/\*_spec.rb\} --format
> documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-factory-bot/ruby-factory-bot_6.2.0-2+rebuild1663007590_amd64-2022-09-12T18:33:11Z.build
To reproduce this, you need ruby-all-dev >= 1:3.0+2. Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it. If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.
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
signature.asc
Description: PGP signature
