ruby-bunny: FTBFS due to faulty testcase
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ruby-bunny (Debian) |
Fix Released
|
Unknown
|
|||
ruby-bunny (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ This is a duplicate of https:/
I've just noticed that ruby-bunny FTBFS when building using a pristine
schroot on sbuild:
--8<---
Waiting for pid file '/tmp/d20200814
## ## RabbitMQ 3.8.5
## ##
########## Copyright (c) 2007-2020 VMware, Inc. or its affiliates.
###### ##
########## Licensed under the MPL 1.1. Website: https:/
Doc guides: https:/
Support: https:/
Tutorials: https:/
Monitoring: https:/
Logs: /<email address hidden>
Config file(s): /tmp/d20200814-
Starting broker... completed with 4 plugins.
Error: operation wait on node bunny@paluero timed out. Timeout value used: 10000
rake aborted!
command failed: ["/usr/
/<<PKGBUILDDIR>
/<<PKGBUILDDIR>
/<<PKGBUILDDIR>
/usr/share/
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>
make[1]: *** [debian/rules:10: override_
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--8<---
If we try to build in a container/VM using dpkg-buildpackage and a
non-root user, the error happens even earlier:
--8<---
Waiting for pid file '/tmp/d20200814
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_
23:47:38.903 [error] CRASH REPORT Process <0.153.0> with 0 neighbours exited with reason: {{shutdown,
{"Kernel pid terminated"
Kernel pid terminated (application_
Crash dump is being written to: erl_crash.
Error: operation wait on node bunny@magical-boa timed out. Timeout value used: 10000
rake aborted!
command failed: ["/usr/
/home/sergio/
/home/sergio/
/home/sergio/
/usr/share/
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/
--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_
fork do
end
pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
run(
run(
end
- The file "bunny.pid" isn't (always) named like that. Here, for
example, it's named "bunny@
following code:
pidfile = File.join($tmpdir, 'mnesia', 'bunny.pid')
run(
- 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.
Changed in ruby-bunny (Debian): | |
status: | Unknown → Fix Released |
I stumbled upon this failure while analyzing the reason for rabbitmq-server's block on the -proposed queue. By the looks of it, the block and this FTBFS are related.