[DRE-maint] Bug#1019637: ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is memoized')

[Antonio Terceiro]

Source: ruby-memoizable
Version: 0.4.2-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-ruby at lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-memoizable with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>      Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is memoized')
> 
>        expected NameError with "No method bar is memoized", got #<NameError: No method bar is memoized
> 
>                fail NameError, "No method #{name} is memoized"
>                ^^^^> with backtrace:
>          # ./lib/memoizable/memory.rb:30:in `block in []'
>          # ./lib/memoizable/memory.rb:29:in `[]'
>          # ./lib/memoizable/module_methods.rb:81:in `unmemoized_instance_method'
>          # ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:6:in `block (2 levels) in <top (required)>'
>          # ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in `block (4 levels) in <top (required)>'
>          # ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in `block (3 levels) in <top (required)>'
>      # ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in `block (3 levels) in <top (required)>'
> 
> Finished in 0.04572 seconds (files took 0.11871 seconds to load)
> 68 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:39 # Memoizable::ModuleMethods#unmemoized_instance_method when the method was not memoized raises an exception
> 
> /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/integration/serializable_spec.rb ./spec/shared/call_super_shared_spec.rb ./spec/unit/memoizable/class_methods/included_spec.rb ./spec/unit/memoizable/instance_methods/freeze_spec.rb ./spec/unit/memoizable/instance_methods/memoize_spec.rb ./spec/unit/memoizable/memory_spec.rb ./spec/unit/memoizable/method_builder/call_spec.rb ./spec/unit/memoizable/method_builder/class_methods/new_spec.rb ./spec/unit/memoizable/method_builder/original_method_spec.rb ./spec/unit/memoizable/module_methods/included_spec.rb ./spec/unit/memoizable/module_methods/memoize_spec.rb ./spec/unit/memoizable/module_methods/memoized_predicate_spec.rb ./spec/unit/memoizable/module_methods/unmemoized_instance_method_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-memoizable/ruby-memoizable_0.4.2-2+rebuild1663007825_amd64-2022-09-12T18:37:06Z.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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20220912/1632eeca/attachment.sig>