Your message dated Thu, 29 Dec 2022 20:07:32 +0100 with message-id <5b902d0c-45f2-bc5b-edc2-a3998e793...@debian.org> and subject line Re: ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|" has caused the Debian Bug report #1022312, regarding ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1022312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-parallel Version: 1.22.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, > '==').strip.should == "Progress: |==|" > > expected: "Progress: |==|" > got: "Ignoring debug-1.4.0 because its extensions are not built. > Try: gem pristine debug --version 1.4.0\n...2.1.0 because its extensions are > not built. Try: gem pristine rbs --version 2.1.0\n\nProgress: |==|" (using ==) > Diff: > @@ -1,3 +1,6 @@ > +Ignoring debug-1.4.0 because its extensions are not built. Try: gem > pristine debug --version 1.4.0 > +Ignoring rbs-2.1.0 because its extensions are not built. Try: gem > pristine rbs --version 2.1.0 > + > Progress: |==| > # ./spec/parallel_spec.rb:681:in `block (3 levels) in <top (required)>' > # ./spec/spec_helper.rb:9:in `block (2 levels) in <top (required)>' > > Finished in 1 minute 18 seconds (files took 0.11327 seconds to load) > 152 examples, 34 failures, 4 pending > > Failed examples: > > rspec './spec/parallel_spec.rb[1:5:10]' # Parallel.map does not queue new > work when one fails in threads > rspec './spec/parallel_spec.rb[1:5:11]' # Parallel.map does not queue new > work when one raises Break in threads > rspec './spec/parallel_spec.rb[1:5:12]' # Parallel.map stops all workers when > a start hook fails with threads > rspec './spec/parallel_spec.rb[1:5:13]' # Parallel.map does not add new work > when a finish hook fails with threads > rspec './spec/parallel_spec.rb[1:5:14]' # Parallel.map does not call the > finish hook when a worker fails with threads > rspec './spec/parallel_spec.rb[1:5:15]' # Parallel.map does not call the > finish hook when a worker raises Break in threads > rspec './spec/parallel_spec.rb[1:5:16]' # Parallel.map does not call the > finish hook when a start hook fails with threads > rspec './spec/parallel_spec.rb[1:5:18]' # Parallel.map sets > Parallel.worker_number with 4 threads > rspec './spec/parallel_spec.rb[1:5:21]' # Parallel.map does not queue new > work when one fails in processes > rspec './spec/parallel_spec.rb[1:5:22]' # Parallel.map does not queue new > work when one raises Break in processes > rspec './spec/parallel_spec.rb[1:5:23]' # Parallel.map stops all workers when > a start hook fails with processes > rspec './spec/parallel_spec.rb[1:5:24]' # Parallel.map does not add new work > when a finish hook fails with processes > rspec './spec/parallel_spec.rb[1:5:25]' # Parallel.map does not call the > finish hook when a worker fails with processes > rspec './spec/parallel_spec.rb[1:5:26]' # Parallel.map does not call the > finish hook when a worker raises Break in processes > rspec './spec/parallel_spec.rb[1:5:27]' # Parallel.map does not call the > finish hook when a start hook fails with processes > rspec './spec/parallel_spec.rb[1:5:29]' # Parallel.map sets > Parallel.worker_number with 4 processes > rspec './spec/parallel_spec.rb[1:5:32]' # Parallel.map does not queue new > work when one fails in ractors > rspec './spec/parallel_spec.rb[1:5:33]' # Parallel.map does not queue new > work when one raises Break in ractors > rspec './spec/parallel_spec.rb[1:5:34]' # Parallel.map stops all workers when > a start hook fails with ractors > rspec './spec/parallel_spec.rb[1:5:35]' # Parallel.map does not add new work > when a finish hook fails with ractors > rspec './spec/parallel_spec.rb[1:5:36]' # Parallel.map does not call the > finish hook when a worker fails with ractors > rspec './spec/parallel_spec.rb[1:5:37]' # Parallel.map does not call the > finish hook when a worker raises Break in ractors > rspec './spec/parallel_spec.rb[1:5:38]' # Parallel.map does not call the > finish hook when a start hook fails with ractors > rspec './spec/parallel_spec.rb[1:10:7]' # Parallel.each works with SQLite in > threads > rspec './spec/parallel_spec.rb[1:10:12]' # Parallel.each does not call the > finish hook when a worker fails with threads > rspec './spec/parallel_spec.rb[1:10:14]' # Parallel.each does not call the > finish hook when a start hook fails with threads > rspec './spec/parallel_spec.rb[1:10:15]' # Parallel.each sets > Parallel.worker_number with threads > rspec './spec/parallel_spec.rb[1:10:16]' # Parallel.each works with SQLite in > processes > rspec './spec/parallel_spec.rb[1:10:21]' # Parallel.each does not call the > finish hook when a worker fails with processes > rspec './spec/parallel_spec.rb[1:10:23]' # Parallel.each does not call the > finish hook when a start hook fails with processes > rspec './spec/parallel_spec.rb[1:10:24]' # Parallel.each sets > Parallel.worker_number with processes > rspec './spec/parallel_spec.rb[1:10:30]' # Parallel.each does not call the > finish hook when a worker fails with ractors > rspec './spec/parallel_spec.rb[1:10:32]' # Parallel.each does not call the > finish hook when a start hook fails with ractors > rspec ./spec/parallel_spec.rb:680 # Parallel progress takes true from > :progress > > /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 --format documentation failed > mv ./.gem2deb.Gemfile.lock Gemfile.lock > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2022/10/23/ruby-parallel_1.22.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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 mine so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---Hi, On Sun, 23 Oct 2022 14:44:15 +0200 Lucas Nussbaum <lu...@debian.org> wrote:> expected: "Progress: |==|" > got: "Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0\n...2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0\n\nProgress: |==|" (using ==) > Diff: > @@ -1,3 +1,6 @@ > +Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0 > +Ignoring rbs-2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0 > + > Progress: |==|This seems to have been the result of the ruby-3.1 transition. Let's close this bug, there's already another FTBFS bug open anyways. (I'll reply there shortly).PaulOpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---