Source: ruby-parallel Version: 1.22.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-parallel with ruby3.1 enabled, the build failed. The failure does not look related to ruby3.1, though, as it fails when running the tests with ruby3.0. Relevant part of the build log (hopefully): > Failure/Error: result.should include 'Wrapper caught SIGINT' > > expected "I should have been killed earlier...\nI should have been > killed earlier...\nFINISHED\n" to include "Wrapper caught SIGINT" > Diff: > @@ -1,3 +1,5 @@ > -Wrapper caught SIGINT > +I should have been killed earlier... > +I should have been killed earlier... > +FINISHED > # ./spec/parallel_spec.rb:135:in `block (4 levels) in <top (required)>' > # ./spec/parallel_spec.rb:11:in `time_taken' > # ./spec/parallel_spec.rb:132:in `block (3 levels) in <top (required)>' > # ./spec/spec_helper.rb:9:in `block (2 levels) in <top (required)>' > > Finished in 1 minute 11.35 seconds (files took 0.119 seconds to load) > 152 examples, 4 failures, 4 pending > > Failed examples: > > rspec ./spec/parallel_spec.rb:102 # Parallel.in_processes kills the processes > when the main process gets killed through ctrl+c > rspec ./spec/parallel_spec.rb:109 # Parallel.in_processes kills the processes > when the main process gets killed through a custom interrupt > rspec ./spec/parallel_spec.rb:122 # Parallel.in_processes does not kill > processes when the main process gets sent an interrupt besides the custom > interrupt > rspec ./spec/parallel_spec.rb:131 # Parallel.in_processes does not kill > threads when the main process gets sent an interrupt besides the custom > interrupt > > /usr/bin/ruby3.0 > -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 --format documentation failed > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby3.0" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-parallel/ruby-parallel_1.22.1-1+rebuild1663007951_amd64-2022-09-12T18:39:11Z.build It seems to fail randomly, differently each time. For example I ran a build locally, and it failed with following -- single -- test failure: ----------------8<----------------8<----------------8<----------------- Failures: 1) Parallel.in_processes does not open unnecessary pipes Failure/Error: `#{RbConfig.ruby} #{cmd}` Timeout::Error: execution expired # ./spec/spec_helper.rb:13:in ``' # ./spec/spec_helper.rb:13:in `ruby' # ./spec/parallel_spec.rb:200:in `block (3 levels) in <top (required)>' # ./spec/spec_helper.rb:9:in `block (2 levels) in <top (required)>' ----------------8<----------------8<----------------8<----------------- 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