Source: ruby-simplecov Version: 0.21.2-1.1 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-simplecov with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > Failure/Error: expect(@stderr).to be_empty > expected `"Ignoring debug-1.4.0 because its extensions are not built. > Try: gem pristine debug --version 1.4.0\nIgnoring rbs-2.1.0 because its > extensions are not built. Try: gem pristine rbs --version 2.1.0\n".empty?` to > be truthy, got false > Shared Example Group: "bad tests" called from > ./spec/return_codes_spec.rb:71 > # ./spec/return_codes_spec.rb:49:in `block (5 levels) in <top > (required)>' > # ./spec/return_codes_spec.rb:12:in `block (4 levels) in <top > (required)>' > # ./spec/return_codes_spec.rb:10:in `chdir' > # ./spec/return_codes_spec.rb:10:in `block (3 levels) in <top > (required)>' > > Finished in 4.1 seconds (files took 0.19282 seconds to load) > 385 examples, 4 failures > > Failed examples: > > rspec './spec/return_codes_spec.rb[1:1:2:1:2]' # return codes inside > fixtures/frameworks when running rspec_good.rb behaves like good tests prints > nothing to STDERR > rspec './spec/return_codes_spec.rb[1:1:3:1:2:2]' # return codes inside > fixtures/frameworks when running testunit_bad.rb behaves like bad tests when > print_error_status is disabled does not print anything to STDERR > rspec './spec/return_codes_spec.rb[1:1:1:1:2]' # return codes inside > fixtures/frameworks when running testunit_good.rb behaves like good tests > prints nothing to STDERR > rspec './spec/return_codes_spec.rb[1:1:4:1:2:2]' # return codes inside > fixtures/frameworks when running rspec_bad.rb behaves like bad tests when > print_error_status is disabled does not print anything to STDERR > > Randomized with seed 48341 > > /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 --exclude-pattern > ./spec/default_formatter_spec.rb,./spec/gemspec_spec.rb --format > documentation failed > mv ./.gem2deb.Gemfile.lock Gemfile.lock > mv test_projects/monorepo/.gem2deb.Gemfile.lock > test_projects/monorepo/Gemfile.lock > mv test_projects/parallel_tests/.gem2deb.Gemfile.lock > test_projects/parallel_tests/Gemfile.lock > mv test_projects/rails/rspec_rails/.gem2deb.Gemfile.lock > test_projects/rails/rspec_rails/Gemfile.lock > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-simplecov/ruby-simplecov_0.21.2-1.1+rebuild1663008205_amd64-2022-09-12T18:43:26Z.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
