[DRE-maint] Bug#1019606: roodi: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: YAML.load_file config_file

Antonio Terceiro terceiro at debian.org
Tue Sep 13 00:16:18 BST 2022


Source: roodi
Version: 5.0.0-4
Severity: serious
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 roodi with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>      Failure/Error: YAML.load_file config_file
> 
>      Psych::DisallowedClass:
>        Tried to load unspecified class: Regexp
>      # (eval):2:in `regexp'
>      # ./lib/roodi/core/runner.rb:135:in `load_config'
>      # ./lib/roodi/core/runner.rb:126:in `load_checks'
>      # ./lib/roodi/core/runner.rb:72:in `check'
>      # ./lib/roodi/core/runner.rb:81:in `check_content'
>      # ./spec/roodi/core/runner_spec.rb:52:in `block (4 levels) in <top (required)>'
> 
> Deprecation Warnings:
> 
> Using `should_not` 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/roodi/checks/abc_metric_method_check_spec.rb:12:in `verify_content_score'.
> 
> Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /<<PKGBUILDDIR>>/spec/roodi/core/runner_spec.rb:58: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.
> 
> 2 deprecation warnings total
> 
> Finished in 0.09081 seconds (files took 0.39761 seconds to load)
> 115 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/roodi/core/runner_spec.rb:7 # Roodi::Core::Runner running against a file adds an error if file is not valid ruby
> rspec ./spec/roodi/core/runner_spec.rb:17 # Roodi::Core::Runner running against a file checks that one file
> rspec ./spec/roodi/core/runner_spec.rb:24 # Roodi::Core::Runner running against a directory checks all files in that directory recursively
> rspec ./spec/roodi/core/runner_spec.rb:31 # Roodi::Core::Runner running without specifying files or directory checks all files in that directory recursively
> rspec ./spec/roodi/core/runner_spec.rb:43 # Roodi::Core::Runner configuration given a custom config file uses check from it
> 
> /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/roodi/checks/abc_metric_method_check_spec.rb spec/roodi/checks/assignment_in_conditional_check_spec.rb spec/roodi/checks/case_missing_else_check_spec.rb spec/roodi/checks/class_line_count_check_spec.rb spec/roodi/checks/class_name_check_spec.rb spec/roodi/checks/class_variable_check_spec.rb spec/roodi/checks/control_coupling_check_spec.rb spec/roodi/checks/core_method_override_check_spec.rb spec/roodi/checks/cyclomatic_complexity_block_check_spec.rb spec/roodi/checks/cyclomatic_complexity_method_check_spec.rb spec/roodi/checks/empty_rescue_body_check_spec.rb spec/roodi/checks/for_loop_check_spec.rb spec/roodi/checks/method_line_count_check_spec.rb spec/roodi/checks/method_name_check_spec.rb spec/roodi/checks/module_line_count_check_spec.rb spec/roodi/checks/module_name_check_spec.rb spec/roodi/checks/npath_complexity_method_check_spec.rb spec/roodi/checks/parameter_number_check_spec.rb spec/roodi/core/runner_spec.rb spec/roodi_task_spec.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/roodi/roodi_5.0.0-4+rebuild1663007308_amd64-2022-09-12T18:28:29Z.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
-------------- 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/7e252b68/attachment.sig>


More information about the Pkg-ruby-extras-maintainers mailing list