Source: ruby-hashie Version: 3.5.5-4 Severity: important 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-hashie with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> expected NoMethodError with "The property 'middle_name' is not defined
> for DashTest.", got #<NoMethodError: The property 'middle_name' is not
> defined for DashTest.
>
> fail NoMethodError, "The property '#{property}' is not defined
> for #{self.class.name}."
> ^^^^> with backtrace:
> # ./lib/hashie/dash.rb:206:in `fail_no_property_error!'
> # ./lib/hashie/dash.rb:184:in `assert_property_exists!'
> # ./lib/hashie/dash.rb:136:in `[]='
> # ./lib/hashie/dash.rb:143:in `block in merge'
> # ./lib/hashie/dash.rb:142:in `each'
> # ./lib/hashie/dash.rb:142:in `merge'
> # ./spec/hashie/dash_spec.rb:266:in `block (4 levels) in <top
> (required)>'
> # ./spec/hashie/dash_spec.rb:266:in `block (3 levels) in <top
> (required)>'
> # ./spec/hashie/dash_spec.rb:266:in `block (3 levels) in <top
> (required)>'
>
> Finished in 0.3638 seconds (files took 0.55129 seconds to load)
> 650 examples, 6 failures
>
> Failed examples:
>
> rspec ./spec/hashie/dash_spec.rb:107 # DashTest errors out for a non-existent
> property
> rspec ./spec/hashie/dash_spec.rb:140 # DashTest writing to properties fails
> writing to a non-existent property using []=
> rspec ./spec/hashie/dash_spec.rb:144 # DashTest writing to properties works
> for an existing property using []=
> rspec ./spec/hashie/dash_spec.rb:157 # DashTest reading from properties fails
> reading from a non-existent property using []
> rspec ./spec/hashie/dash_spec.rb:222 # DashTest#new fails with non-existent
> properties
> rspec ./spec/hashie/dash_spec.rb:265 # DashTest#merge fails with non-existent
> properties
>
> /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
> ./spec/hashie/array_spec.rb ./spec/hashie/clash_spec.rb
> ./spec/hashie/dash_spec.rb ./spec/hashie/extensions/autoload_spec.rb
> ./spec/hashie/extensions/coercion_spec.rb
> ./spec/hashie/extensions/dash/coercion_spec.rb
> ./spec/hashie/extensions/dash/indifferent_access_spec.rb
> ./spec/hashie/extensions/deep_fetch_spec.rb
> ./spec/hashie/extensions/deep_find_spec.rb
> ./spec/hashie/extensions/deep_locate_spec.rb
> ./spec/hashie/extensions/deep_merge_spec.rb
> ./spec/hashie/extensions/ignore_undeclared_spec.rb
> ./spec/hashie/extensions/indifferent_access_spec.rb
> ./spec/hashie/extensions/indifferent_access_with_rails_hwia_spec.rb
> ./spec/hashie/extensions/key_conversion_spec.rb
> ./spec/hashie/extensions/mash/keep_original_keys_spec.rb
> ./spec/hashie/extensions/mash/safe_assignment_spec.rb
> ./spec/hashie/extensions/mash/symbolize_keys_spec.rb
> ./spec/hashie/extensions/merge_initializer_spec.rb
> ./spec/hashie/extensions/method_access_spec.rb
> ./spec/hashie/extensions/strict_key_access_spec.rb
> ./spec/hashie/extensions/stringify_keys_spec.rb
> ./spec/hashie/extensions/symbolize_keys_spec.rb ./spec/hashie/hash_spec.rb
> ./spec/hashie/mash_spec.rb ./spec/hashie/parsers/yaml_erb_parser_spec.rb
> ./spec/hashie/rash_spec.rb ./spec/hashie/trash_spec.rb
> ./spec/hashie/utils_spec.rb ./spec/hashie/version_spec.rb
> ./spec/hashie_spec.rb ./spec/integration/omniauth/integration_spec.rb
> ./spec/integration/rails-without-dependency/integration_spec.rb --format
> documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-hashie/ruby-hashie_3.5.5-4+rebuild1663007681_amd64-2022-09-12T18:34:42Z.build
To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough. 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
