Source: krb5 Version: 1.20.1-6 Severity: serious Tags: ftbfs X-Debbugs-CC: jspri...@debian.org
Filing with severity: serious as the buildd network has started switching to sbuild with unshare backend, and multiple people have reproduced this problem. When building krb5 with sbuild, configured to use the unshare backend, the t_iprop.py test apparently times out without any output. Last few lines: | PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_general.py | PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_hooks.py | PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_dump.py | PYTHONPATH=../../src/util VALGRIND="" python3 ../../src/tests/t_iprop.py | E: Build killed with signal TERM after 60 minutes of inactivity I'm attaching my own build log, running on arm64. Another build log showing the same problem can be found here (ran on amd64): https://people.debian.org/~sanvila/unshare/unstable-20240529/krb5_1.20.1-6_amd64-20240529T214515.396Z My build log shows the result of an external SIGTERM instead of sbuild killing it, but that's just a distracting detail. I'll note this appears unrelated to #1063648. Chris
krb5_1.20.1-6_arm64-killed.build.gz
Description: application/gzip
