Package: bashdb
Version: 4.3.0.91+ds-1
Severity: important
Tags: upstream patch
Dear Maintainer,
* The package passed extensive FTBS testing but failed when it hit
the reproducibility site (jenkins). Here is an extract of the log:
FAIL: test-sig
.....
============================================================================
Testsuite summary for bashdb 4.3-0.91
============================================================================
# TOTAL: 42
# PASS: 38
# SKIP: 3
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See test/integration/test-suite.log
Please report to [email protected]
============================================================================
Makefile:619: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/tmp/buildd/bashdb-4.3.0.91+ds/test/integration'
Makefile:725: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/tmp/buildd/bashdb-4.3.0.91+ds/test/integration'
Makefile:1071: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/tmp/buildd/bashdb-4.3.0.91+ds/test/integration'
Makefile:357: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/tmp/buildd/bashdb-4.3.0.91+ds/test'
Makefile:575: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/tmp/buildd/bashdb-4.3.0.91+ds'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
The test-sig test was always generating a SEGV, but this was only being found on
jenkins. So there were essentially two causes:
1. The run_debugger function did not check the exit status of the debgger and
flag up an error.
2. The test-sig test sent commands to the debbgger after the debugged script
had died.
Separate patches will be applied for both causes. These will be sent upstream.
We hope upstream
will apply 1. as is, but 2. really needs more work. The patched behaviour will
mean some
behaviour that was supposed to be tested is not tested.
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bashdb depends on:
pn python:any <none>
bashdb recommends no packages.
bashdb suggests no packages.
-- no debconf information
