Your message dated Thu, 20 Aug 2020 18:35:08 +0000
with message-id <[email protected]>
and subject line Bug#968420: fixed in ruby-bunny 2.14.4-4
has caused the Debian Bug report #968420,
regarding ruby-bunny: FTBFS due to faulty testcase
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 [email protected]
immediately.)
--
968420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968420
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-bunny
Version: 2.14.4-3
Severity: serious
Tags: ftbfs sid
I've just noticed that ruby-bunny FTBFS when building using a pristine
schroot on sbuild:
--8<---------------cut here---------------start------------->8---
Waiting for pid file '/tmp/d20200814-17660-k3x0b6/mnesia/bunny.pid' to appear
## ## RabbitMQ 3.8.5
## ##
########## Copyright (c) 2007-2020 VMware, Inc. or its affiliates.
###### ##
########## Licensed under the MPL 1.1. Website: https://rabbitmq.com
Doc guides: https://rabbitmq.com/documentation.html
Support: https://rabbitmq.com/contact.html
Tutorials: https://rabbitmq.com/getstarted.html
Monitoring: https://rabbitmq.com/monitoring.html
Logs: /tmp/d20200814-17660-k3x0b6/log/[email protected]
/tmp/d20200814-17660-k3x0b6/log/bunny@paluero_upgrade.log
Config file(s): /tmp/d20200814-17660-k3x0b6/rabbitmq.conf
Starting broker... completed with 4 plugins.
Error: operation wait on node bunny@paluero timed out. Timeout value used: 10000
rake aborted!
command failed: ["/usr/lib/rabbitmq/bin/rabbitmqctl", "wait",
"/tmp/d20200814-17660-k3x0b6/mnesia/bunny.pid"]
/<<PKGBUILDDIR>>/debian/ruby-tests.rake:53:in `run'
/<<PKGBUILDDIR>>/debian/ruby-tests.rake:62:in `start_rabbitmq_server'
/<<PKGBUILDDIR>>/debian/ruby-tests.rake:75:in `block in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `<top
(required)>'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-bunny
returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_install] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--8<---------------cut here---------------end--------------->8---
If we try to build in a container/VM using dpkg-buildpackage and a
non-root user, the error happens even earlier:
--8<---------------cut here---------------start------------->8---
Waiting for pid file '/tmp/d20200814-28938-5mzc2m/mnesia/bunny.pid' to appear
23:47:37.895 [error]
23:47:37.899 [error] BOOT FAILED
BOOT FAILED
23:47:37.899 [error] ===========
===========
23:47:37.900 [error] ERROR: distribution port 25672 in use by rabbit@magical-boa
ERROR: distribution port 25672 in use by rabbit@magical-boa
23:47:37.900 [error]
23:47:38.902 [error] Supervisor rabbit_prelaunch_sup had child prelaunch
started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit
with reason {dist_port_already_used,25672,"rabbit","magical-boa"} in context
start_error
23:47:38.903 [error] CRASH REPORT Process <0.153.0> with 0 neighbours exited
with reason:
{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","magical-boa"}}},{rabbit_prelaunch_app,start,[normal,[]]}}
in application_master:init/4 line 138
{"Kernel pid
terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,\"rabbit\",\"magical-boa\"}}},{rabbit_prelaunch_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller)
({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{dist_port_already_used,25672,"rabbit","magical-boa"}}},{rabbi
Crash dump is being written to: erl_crash.dump...done
Error: operation wait on node bunny@magical-boa timed out. Timeout value used:
10000
rake aborted!
command failed: ["/usr/lib/rabbitmq/bin/rabbitmqctl", "wait",
"/tmp/d20200814-28938-5mzc2m/mnesia/bunny.pid"]
/home/sergio/ruby-bunny/debian/ruby-tests.rake:53:in `run'
/home/sergio/ruby-bunny/debian/ruby-tests.rake:62:in `start_rabbitmq_server'
/home/sergio/ruby-bunny/debian/ruby-tests.rake:75:in `block in <top (required)>'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `<top
(required)>'
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.7" failed. Exiting.
dh_auto_install: error: dh_ruby --install
/home/sergio/ruby-bunny/debian/ruby-bunny returned exit code 1
--8<---------------cut here---------------end--------------->8---
There are a few problems with the testcase:
- As stated above, it can't run under as a non-root user. For example,
this won't work:
def start_rabbitmq_server
fork do
exec('/usr/lib/rabbitmq/bin/rabbitmq-server')
end
pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
run('/usr/lib/rabbitmq/bin/rabbitmqctl', 'wait', pidfile)
run('./bin/ci/before_build')
end
- The file "bunny.pid" isn't (always) named like that. Here, for
example, it's named "bunny@${HOST}.pid". This will break the
following code:
pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
run('/usr/lib/rabbitmq/bin/rabbitmqctl', 'wait', pidfile)
- It tries to "pkill epmd", which also won't work when run as non-root.
It seems to me like this test should be executed by autopkgtest, because
the operations listed above would then be able to succeed.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-bunny
Source-Version: 2.14.4-4
Done: Sergio Durigan Junior <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ruby-bunny, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergio Durigan Junior <[email protected]> (supplier of updated ruby-bunny
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 20 Aug 2020 10:55:09 -0400
Source: ruby-bunny
Architecture: source
Version: 2.14.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
<[email protected]>
Changed-By: Sergio Durigan Junior <[email protected]>
Closes: 968420
Changes:
ruby-bunny (2.14.4-4) unstable; urgency=medium
.
* Team upload.
.
[ Lucas Kanashiro ]
* d/ruby-tests.rake: add a reminder to revisit the blacklisted spec file
* d/control: update the Homepage url, the former does not work
.
[ Sergio Durigan Junior ]
* Adjust test infrastructure to use a customized rabbitmq-server.
In order to perform our tests, we have to install the rabbitmq-server
package. This means that when we build the package outside a chroot,
the systemd service of rabbitmq-server is started automatically. This
is expected behaviour, but it conflicts with what the setup step of
our tests does: it tries to start its own instance of rabbitmq-server
using a customized configuration file.
In order to overcome this problem, it is possible to start another
instance of rabbitmq-server listening at a different port. This is
what this commit does, which ultimately fixes a FTBFS that happens
when building ruby-bunny outside a chroot. Unfortunately, the
solution here is a bit hacky and prone to failures, but it works
reasonably well enough that I think it's safe to adopt it into
package.
- d/ruby-tests.rake: Use Socket.gethostname to compose the pidfile
name.
- d/rules: On override_dh_auto_install, adjust the local rabbitmq.conf
file and instruct it to listen on localhost:16688; adjust several
environment variables needed to properly start rabbitmq-server and
ruby-bunny at the customized port; adjust the tests inside spec/ and
make sure they explicitly connect to the rabbitmq-server instance
running on the customized port. (Closes: #968420) (LP: #1891842)
Checksums-Sha1:
651e2bb067ce974c604c1f33c11c9fee1d27cb3e 2242 ruby-bunny_2.14.4-4.dsc
a6875cfb9fabc909b64166d87fbe3b83bf278679 7236 ruby-bunny_2.14.4-4.debian.tar.xz
4a00ce7c971d3cb2044193ab977909818d6efaff 9818
ruby-bunny_2.14.4-4_amd64.buildinfo
Checksums-Sha256:
26d89e2d9f60bb13df8fb828d7767a2af2e2922c435a1fb6779563de0dc323bb 2242
ruby-bunny_2.14.4-4.dsc
af298d3ab2362531d0ac0fa62a187078988a491718a4a12f2e292b1850eb37bb 7236
ruby-bunny_2.14.4-4.debian.tar.xz
c13979c7f738fe898037f825b68bf57743b96ac596971a7cfb0e5df0b37bc9e2 9818
ruby-bunny_2.14.4-4_amd64.buildinfo
Files:
8d14a5eddd78329e1e9c130dff5b8bb2 2242 ruby optional ruby-bunny_2.14.4-4.dsc
83e6cf88f0ff4bc9c860088bfadda463 7236 ruby optional
ruby-bunny_2.14.4-4.debian.tar.xz
d2ab842941c5a22b4de585b235993756 9818 ruby optional
ruby-bunny_2.14.4-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl8+vWwVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8flEQAIMDxFkECPiWurbebuqwNegKRETc
TcPKAP2a03I1mE5m/4ODlCjXKAofFbZY8Npy/90xcmDbx8M/cnKmnXIYILLUFkC2
cjbMMO7X7H7jf7QZGJQlIvEI0uq4I/va0memWe0DaqKWWg1u62DRj/PE7j0DSIBU
v2UMMoqQISRvHkcBbVQq6z19xfjarwNesZc+sOKxorUTfQX6GY7HVcQ2m/k4IN78
ygjLHU4CQVFJKs+sPoxgoXQiYIpSJHJEIRGrF/zXKAVCub2JIz4/tNEPun9zG93J
9jBD3lzaFhMVCaUkDSPZ9FHwPylzmuJzfhR5FBEY22o7ERroio6cfcFAp3EVmmK9
AyDBOa+LPsAu6vyK3RJPbWZwops0U8H9MvO48dvOj+mN9QBLheoE5o5lfUQu2p86
Ee4a2pTFOpVKa3gmFLsW8dpWpz6ULFw29UraWncfwB0/EWbd/ilOvZIyy1+d5N9Q
vpvmjPY+jERXL8MT8ODdFEKO+U5q2TSyJYZ70edZOYxgAsZBKS1qfECNJo67RnSo
Ue0BaVddBeb+zn5PhJ3xmMUZiu5+HT45vow60xcp41uKJVLDAQAjPqabwpBIXqSt
Ug6kFgz/95NP+SNTSB0RX0qiM6l8CQd9Dp3XWA11YH53v79eg67R/ePfzZlHksdv
UgrgCSfoCEz26UX+
=iOXB
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
