Source: topydo Version: 0.13-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: issue
Dear David, I have no idea what's happening, but currently we have multiple workers (on different architectures) off-line on the ci.debian.net infrastructure. In the current (short) list of pending tests, todo.txt-base sticks out as being triggered (by topydo) some time ago and waiting on all architectures. armhf finished (tmpfail) while I was writing this message so I noticed it already ran multiple times but the test on armhf times out after 2:55 hours (previous tests were under 1 minute) with an error in autopkgtest so is treated as tmpfail (and retried). Can you help us investigate what's going on? What is topydo doing? Anything that sparks your brain when I say that I'm seeing (sleeping) processes, number of threads, CPU usage, file table usage and memory peak just before the workers go off-line? Our armhf worker is a very powerful machine, the test seems to require around 300k open files and 80 GB of RAM before it hangs. Paul
OpenPGP_signature
Description: OpenPGP digital signature
