Hey, I have uploaded 3.11 and 3.11.1 to the Debian build servers and most of the builds are failing with a stuck testsuite. I cannot reproduce the bug locally. Automated builds are being killed after 150 minutes of no activity (ie no terminal output).
I don't see a pattern in the architectures that fail, though. Command line help output 40: standard help output ok 41: standard usage output ok 42: MU_PARSEOPT_PROG_NAME ok 43: MU_PARSEOPT_PROG_DOC ok 44: MU_PARSEOPT_PROG_ARGS ok 45: MU_PARSEOPT_BUG_ADDRESS ok 46: MU_PARSEOPT_PACKAGE_NAME and MU_PARSEOPT_PACKAGE_URL ok 47: all data ok 48: ARGP_HELP_FMT compatibility ok 49: ARGP_HELP_FMT usage compatibility ok 50: MU_PARSEOPT_VERSION_HOOK usage output ok 51: MU_PARSEOPT_VERSION_HOOK help output ok 52: MU_PARSEOPT_PROG_ARGS (alternative) ok Standard streams 53: strin ok 54: strout E: Build killed with signal TERM after 150 minutes of inactivity Any ideas, Sergey? Jordi -- Jordi Mallach <jo...@debian.org> Debian Project
