Source: bbmap Version: 39.20+dfsg-2 Severity: important User: [email protected] Usertags: flaky
Dear maintainer(s),I looked at the results of the autopkgtest of your package because I was investigating memory issues on our ci.d.n infrastructure. I noticed that your package uses an insane amount of memory.
On our amd64 worker, I saw it peaking at 51% of 250 GB. On our loong64 worker I saw it peaking at 83% of 127 GB. Now there's an argument to make that the infra should protect itself against this kind of misbehavior, but currently it doesn't (we're working on that). I would appreciate it if you limit the test on memory usage.
In the past I already added a reject list entry on riscv64 as the test times out. It also seems to take much more time on loong64 than on other architectures, so I'm also going to add it to the reject list for loong64 too. You don't need to investigate this as riscv64 has some under powered workers so I consider that an infrastructure problem and loong64 isn't a release architecture yet, but solutions for both architectures are welcome.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
