[DRE-maint] Bug#980582: roodi: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: errors[0].to_s.should match(/dummy-file.rb:[1-2] - Case statement is missing an else clause./)

[Lucas Nussbaum]

Source: roodi
Version: 5.0.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>      Failure/Error: errors[0].to_s.should match(/dummy-file.rb:[1-2] - Case statement is missing an else clause./)
> 
>        expected "dummy-file.rb looks like it's not a valid Ruby file." to match /dummy-file.rb:[1-2] - Case statement is missing an else clause./
>        Diff:
>        @@ -1 +1 @@
>        -/dummy-file.rb:[1-2] - Case statement is missing an else clause./
>        +"dummy-file.rb looks like it's not a valid Ruby file."
>      # ./spec/roodi/checks/case_missing_else_check_spec.rb:30:in `block (2 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.58011 seconds (files took 0.42169 seconds to load)
> 115 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/roodi/checks/case_missing_else_check_spec.rb:8 # Roodi::Checks::CaseMissingElseCheck should accept case statements that do have an else
> rspec ./spec/roodi/checks/case_missing_else_check_spec.rb:20 # Roodi::Checks::CaseMissingElseCheck should reject case statements that do have an else
> 
> /usr/bin/ruby2.7 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/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 "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/roodi_5.0.0-3_unstable.log

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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.