Source: rsyslog Version: 8.2608.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: [email protected], [email protected] User: [email protected] Usertags: amd64 User: [email protected] Usertags: environment
Hi Michael, rsyslog currently fails to build on reproduce.debian.net making it blocked from migration to testing. The error seems to be: 09:21:38 wait_file_lines waiting, expected 10000, current 9454 lines wait_file_lines failed, expected 10000 got 9454 after 1787476899 retries, took 90 seconds Core dump policy: ulimit -c: unlimited kernel.core_pattern: core kernel.core_uses_pid: 1 fs.suid_dumpable: 0 No owned rsyslogd core dumps found === Error Logs Collection === gather-check-logs.sh not found, collecting available logs manually... No failed-tests.log found not reporting failure as RSYSLOG_STATSURL is not set rsyslog pid file still exists, trying to shutdown... rsyslogd debug: info: trying to cooperatively stop input imdiag, timeout 60000 ms rsyslogd debug: info: trying to cooperatively stop input imfile, timeout 60000 ms 09:21:39[99] FAIL: Test ./imfile-logrotate-async.sh (took 99 seconds) FAIL imfile-logrotate-async.sh (exit status: 1) rsyslog debug: main Q:Reg/w0: enter WrkrExecCleanup rsyslog debug: 0x560e0052df60: worker exiting rsyslog debug: main Q:Reg/w0: thread joined https://reproduce.debian.net/amd64/api/v1/builds/282149/log >From my tests reproducing this seems to depend a lot on the host and it seems to happen more often when compiled on ext4 (as does reproduce.d.n right now) then on tmpfs (as used by the buildds). Feel free to reach out if you need help. Cheers Jochen
