Source: gdb, procdump Control: found -1 gdb/17.2-1 Control: found -1 procdump/2.2-4 Severity: serious Tags: sid forky User: [email protected] Usertags: breaks needs-update
Dear maintainer(s),With a recent binNMU of gdb the autopkgtest of procdump fails in testing when that autopkgtest is run on i386 with the new binary packages of gdb from unstable. It passes when run with only packages from testing. In tabular form:
pass fail
gdb from testing 17.2-1 (binNMU)
procdump from testing 2.2-4
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of gdb to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
It seems that the error is coming from the lack of a coredump that is intended to fail the test several only several lines later:
https://sources.debian.org/src/procdump/2.2-4/debian/tests/run.sh#L28 More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gdb https://ci.debian.net/data/autopkgtest/testing/i386/p/procdump/72739897/log.gz 38s TASK PID = 1814 38s -rwxr-xr-x 1 root root 3487072 Mar 28 2025 /usr/bin/procdump 38s PROCDUMP PID = 181838s root 1818 0.0 0.0 238996 2840 ? Dl 12:18 0:00 procdump -pgid 0 -n 1 38s root 1820 0.0 0.0 6300 2384 ? S 12:18 0:00 grep -i 1818
48s Killing 1814 48s Killing 1818 48s ls: cannot access 'sh_time*': No such file or directory 48s Cores dumped: 0 48s Failed 49s autopkgtest [12:18:23]: test run.sh
OpenPGP_signature.asc
Description: OpenPGP digital signature
