[DRE-maint] Bug#1139980: ruby-bunny: FTBFS: flaky test: Failed examples: rspec ./spec/higher_level_api/integration/basic_reject_spec.rb:132 # Bunny::Channel#basic_reject with requeue = default rejects a message

Santiago Vila sanvila at debian.org
Sun Jun 14 10:50:58 BST 2026


Package: src:ruby-bunny
Version: 3.1.0-1
Severity: serious
Tags: ftbfs forky sid

Hello Antonio et al.

This failure happens randomly, but I get a failure rate around 38% on machines
with 1 CPU and around 66% on machines with 2 CPUs (tried 20 times at least
in each case), which is bad enough for a stable release.

Follows my standard template for FTBFS bugs:

--------------------------------------------------------------------------

Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202606/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

Caveat: The above should be understood as "where the reported randomness happens".

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:ruby-bunny, so that this is still
visible in the BTS web page for this package.

Thanks.

--------------------------------------------------------------------------------
[...]
Failures:

  1) Bunny::Channel#basic_reject with requeue = default rejects a message
     Failure/Error: q  = ch.queue("bunny.basic.reject.with-requeue-false", exclusive: true)

     Bunny::ResourceLocked:
       RESOURCE_LOCKED - cannot obtain exclusive access to locked queue 'bunny.basic.reject.with-requeue-false' in vhost 'bunny_testbed'. It could be originally declared on another connection or the exclusive property value does not match that of the original...
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/channel.rb:2730:in `raise_if_continuation_resulted_in_a_channel_error!'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/channel.rb:1412:in `queue_declare_without_recording_topology'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/channel.rb:1368:in `queue_declare'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/queue.rb:391:in `declare!'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/queue.rb:90:in `initialize'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/channel.rb:526:in `new'
     # /<<PKGBUILDDIR>>/debian/ruby-bunny/usr/share/rubygems-integration/all/gems/bunny-3.1.0/lib/bunny/channel.rb:526:in `queue'
     # ./spec/higher_level_api/integration/basic_reject_spec.rb:134:in `block (3 levels) in <top (required)>'

Finished in 3 minutes 33.1 seconds (files took 0.17811 seconds to load)
489 examples, 1 failure

Failed examples:

rspec ./spec/higher_level_api/integration/basic_reject_spec.rb:132 # Bunny::Channel#basic_reject with requeue = default rejects a message

/usr/bin/ruby3.3 -I/usr/share/rubygems-integration/all/gems/ [too-long-redacted] b --format documentation failed
Stopping and halting node bunny at sbuild ...
Gracefully halting Erlang VM
/usr/lib/ruby/vendor_ruby/gem2deb.rb:52:in `run': /usr/bin/ruby3.3 /usr/bin/gem2deb-test-runner (Gem2Deb::CommandFailed)
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:64:in `block in run_ruby'
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:87:in `maybe_crossbuild'
	from /usr/lib/ruby/vendor_ruby/gem2deb.rb:63:in `run_ruby'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:189:in `run_tests_for_version'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:176:in `block in run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:175:in `each'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:175:in `run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:71:in `run_tests'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:57:in `install'
	from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:163:in `install'
	from /usr/bin/dh_ruby:89:in `<main>'
dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-bunny returned exit code 1
make[1]: *** [debian/rules:12: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------



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