Your message dated Tue, 29 Oct 2024 01:51:53 +0000
with message-id <e1t5boj-005t1u...@fasolo.debian.org>
and subject line Bug#1086148: fixed in dbus 1.14.10-6
has caused the Debian Bug report #1086148,
regarding dbus: FTBFS: ERROR: test-bus-dispatch - exited with status 134
(terminated by signal 6?)
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.)
--
1086148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dbus
Version: 1.14.10-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-ri...@lists.debian.org
User: debian-ri...@lists.debian.org
Usertags: riscv64
Dear maintainer,
dbus version 1.14.10-5 fails to build on the riscv64 buildd. Here are the
relevant parts of the build log:
| ERROR: test-bus-dispatch - missing test plan
| ERROR: test-bus-dispatch - exited with status 134 (terminated by signal 6?)
...
| ERROR: test-bus-dispatch
| ========================
...
| ok 9 - bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_shell_fail_service_auto_start
| PASS: test-bus-dispatch 9 -
bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_shell_fail_service_auto_start
| ok 10 - bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_existent_service_auto_start
| PASS: test-bus-dispatch 10 -
bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_existent_service_auto_start
| ok 11 - bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_shell_service_success_auto_start
| PASS: test-bus-dispatch 11 -
bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf -
check_shell_service_success_auto_start
| ok 12 - bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf
| PASS: test-bus-dispatch 12 -
bus_dispatch_test_conf:valid-config-files/debug-allow-all.conf
| #
bus_dispatch_test_conf:valid-config-files-system/debug-allow-all-pass.conf...
| ERROR: test-bus-dispatch - missing test plan
| ERROR: test-bus-dispatch - exited with status 134 (terminated by signal 6?)
The full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=dbus&arch=riscv64&ver=1.14.10-5&stamp=1729988710&raw=0
The problem is actually not specific to riscv64 and can be easily
reproduced on any system running testing/unstable like the riscv64 build
daemons. On the other hand it can't be reproduced on a system running
stable. Here is the corresponding backtrace:
| #0 __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
| tid = <optimized out>
| ret = 0
| pd = <optimized out>
| old_mask = {__val = {206158430212}}
| ret = <optimized out>
| #1 0x00007f71bd122ebf in __pthread_kill_internal (threadid=<optimized out>,
signo=6) at ./nptl/pthread_kill.c:78
| No locals.
| #2 0x00007f71bd0cec82 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
| ret = <optimized out>
| #3 0x00007f71bd0b74f0 in __GI_abort () at ./stdlib/abort.c:79
| save_stage = 1
| act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction =
0x20}, sa_mask = {__val = {140126481511648, 140126481502192, 140126481511779,
1, 140126480070738, 1, 10, 94622353875920,
| 94622353869440, 140725391239648, 140126480074297,
140126481511648, 140126480075619, 140126481512096, 94622100705737,
94622353875920}}, sa_flags = -1123213280,
| sa_restorer = 0x560eecb351c9}
| #4 0x00007f71bd37f085 in _dbus_abort () at ../../../dbus/dbus-sysdeps.c:101
| s = <optimized out>
| #5 0x00007f71bd3bb9d0 in _dbus_warn (format=format@entry=0x560eecb351c9 "Did
not expect error %s") at ../../../dbus/dbus-internals.c:257
| severity = <optimized out>
| args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area =
0x7ffd2ef4a950, reg_save_area = 0x7ffd2ef4a890}}
| #6 0x0000560eecb0f3b9 in check_list_services (context=<optimized out>,
connection=0x560efbca4a80) at ../../../bus/dispatch.c:4618
| message = 0x560efbca63d0
| base_service_message = 0x0
| retval = <optimized out>
| flags = 0
| base_service = 0x560e00000000 <error: Cannot access memory at address
0x560e00000000>
| serial = 8
| existent = 0x560eecb3b1e8 "org.freedesktop.DBus.TestSuiteEchoService"
| services = 0x560efbca8010
| len = 5
| message = <optimized out>
| base_service_message = <optimized out>
| base_service = <optimized out>
| serial = <optimized out>
| retval = <optimized out>
| existent = <optimized out>
| flags = <optimized out>
| services = <optimized out>
| len = <optimized out>
| __func__ = "check_list_services"
| out = <optimized out>
| message_kind = <optimized out>
| #7 bus_dispatch_test_conf (test_data_dir=test_data_dir@entry=0x7ffd2ef4aab0,
filename=filename@entry=0x560eecb3ca30
"valid-config-files-system/debug-allow-all-pass.conf",
| use_launcher=use_launcher@entry=1) at ../../../bus/dispatch.c:4888
| context = <optimized out>
| foo = <optimized out>
| bar = 0x560efbc856b0
| baz = 0x560efbca4a80
| error = {name = 0x0, message = 0x0, dummy1 = 1, dummy2 = 1, dummy3 =
0, dummy4 = 0, dummy5 = 1, padding1 = 0xffffffff}
| __func__ = "bus_dispatch_test_conf"
| #8 0x0000560eecb107c5 in bus_dispatch_test (test_data_dir_cstr=<optimized
out>) at ../../../bus/dispatch.c:5056
| test_data_dir = {dummy1 = 0x560efbc78910, dummy2 = 73, dummy3 = 81,
dummy_bit1 = 1, dummy_bit2 = 1, dummy_bit3 = 1, dummy_bits = 0}
| __func__ = "bus_dispatch_test"
| #9 0x0000560eecb33102 in _dbus_test_main (argc=<optimized out>,
argv=<optimized out>, n_tests=n_tests@entry=1, tests=tests@entry=0x560eecb53010
<test>,
| flags=flags@entry=(DBUS_TEST_FLAGS_REQUIRE_DATA |
DBUS_TEST_FLAGS_CHECK_MEMORY_LEAKS | DBUS_TEST_FLAGS_CHECK_FD_LEAKS),
test_pre_hook=test_pre_hook@entry=0x560eecafad70 <test_pre_hook>,
| test_post_hook=0x560eecafad80 <test_post_hook>) at
../../../test/test-utils.c:828
| before = 5515908
| after = 94622100716651
| initial_fds = 0x560efbc7b550
| test_data_dir = <optimized out>
| specific_test = 0x4 <error: Cannot access memory at address 0x4>
| i = 0
| #10 0x0000560eecafac6e in main (argc=<optimized out>, argv=<optimized out>)
at ../../../test/bus/dispatch.c:57
I have tracked down the issue to the use of systemd >= 256~rc3-3 on the
host, which bumps the maximum number of open files hard limit from
1048576 to 1073741816 [1].
Restoring the bookworm value using "ulimit -Hn 1048576" before the build
is enough to fix the issue.
Regards
Aurelien
[1]
https://salsa.debian.org/systemd-team/systemd/-/commit/99066f931bb49b43e7282fc1fe8488373bfb81e5
--- End Message ---
--- Begin Message ---
Source: dbus
Source-Version: 1.14.10-6
Done: Simon McVittie <s...@debian.org>
We believe that the bug you reported is fixed in the latest version of
dbus, 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 1086...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <s...@debian.org> (supplier of updated dbus 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 ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 28 Oct 2024 22:02:49 +0000
Source: dbus
Architecture: source
Version: 1.14.10-6
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@debian.org>
Closes: 1086148
Changes:
dbus (1.14.10-6) unstable; urgency=medium
.
* d/p/tests-Only-check-whether-the-first-1024-fds-are-close-on-.patch:
Fix FTBFS when running with a high rlimit.
Thanks to Aurelien Jarno for diagnosing the root cause.
(Closes: #1086148)
Checksums-Sha1:
6f355267193e6f156e2461b0449a2abf5c3e64d6 3743 dbus_1.14.10-6.dsc
b6bf5dfda496a357dd2b666f9715ecf8600171e9 64868 dbus_1.14.10-6.debian.tar.xz
21371bdcc541e87c0c903a3aca7ee62fa3251794 7877 dbus_1.14.10-6_source.buildinfo
Checksums-Sha256:
645f06698b6a02816c715b01423ed4cdf4c58634727fbcd1f29cadaa44e50196 3743
dbus_1.14.10-6.dsc
4df4ccf531b82e437b294ecacd9c72a169ab17cadb6828e56cf9f7fdfe1d42c4 64868
dbus_1.14.10-6.debian.tar.xz
85252d6ee5f49942b6410e1e963c21f94d3c31edcf9b33c713ead79b485a920c 7877
dbus_1.14.10-6_source.buildinfo
Files:
db6f60e0f6956eb4844106dcc547cb9b 3743 admin optional dbus_1.14.10-6.dsc
4580e4f516670c442888c10c86c927bb 64868 admin optional
dbus_1.14.10-6.debian.tar.xz
3ca0967942b7368db51fcf4185f838db 7877 admin optional
dbus_1.14.10-6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmcgHpAACgkQI1wJnT6z
MHZDFRAAohteqn02xm8Gqb3xz2ZdfMNVMAQNW87VLq+5LChaeKwho6jVV9kkIB7V
d3lixafII2xSoj8b/4icCz7+2EqIP7L5bNMtlhaX9ZXzNyPYMvjEVfOVsf4ph1Nv
RhdWtCefy4yHEoKlNdv0j3W/vaZ7H7dcVSlki9tW+0m/5keqYshOGQvAhKL1g5dH
l5kipkRwG5FSgzvVYhkPzALSm4bmM9ld7qzJkleyE2cx4gO3YoSKFpgoZnbmvJE/
U5pcUXPf8gdcRH/BLx+EjxARl22iiaO2fxHFM5OFasnzTxMCDFTZ/QSznuUbUOxy
S1wvd2oaQ28dW1QmmDaWW65e9Tl2WGqsbqwrJfBxVAPPMihjSxDqBRfOpllTlf+O
WQvnMxg50C//A/uiOOjgNPCpamMzDRCjK/mClicKrXO4OemJlzyPJ5GGvXNnOyOm
EQmyk96qxpXil++0yQdoZvZCtBuoa5VmJnc6nwy5XJYegg5tXUP7ojLHWhns/y60
EEqMrj4OI81Z15ttXqWRYSUB4OLo6i+gExcewTCVhTnTgyZMP0tnDS6TvNb9kDr+
8ehUBTEiOAR4q0UGUEq2tRaviJqiQs5Y+N4gO9wGp0k/HvmPuD+3NU+2ycCZvi1K
yJbXoeqbOGk5z62fRaL0RXFU67Z4Mt60pSzuqesMvQ163+YkAYY=
=HVRY
-----END PGP SIGNATURE-----
pgpuhgaysVfQV.pgp
Description: PGP signature
--- End Message ---
