Source: libthrust Version: 1.15.0-1 Severity: normal X-Debbugs-Cc: debian...@list.debian.org
Dear maintainer, I was checking what was happening on our infrastructure as I was seeing degraded performance on several architectures, including several host running out of disk space and even one VM that hang. I don't have solid evidence that it's all caused by libthrust, but the results on amd64, arm64 and ppc64el don't inspire confidence that this package is entirely "innocent". Please consider making your test suite much less intense. Looking at our the stats [1] of our big amd64 worker, it really looks like the test was stressing it so much that we were building up a backlog of tests, which rarely happens on amd64. Your test on amd64 [2] took 12 hours to come to a "neutral" conclusion because 4 of them timed out (but marked flaky) and all others failed (while marked flaky) or passed while marked superficial. That's a poor result for such an extreme test. On arm64 and ppc64el your tests seem to tmpfail. I am *suspecting* that is because they run out of diskspace. All our arm64 and ppc64el workers have 40 GB disk and run two debci instances in parallel. For now, I have put libthrust on our rejectlist for those three architectures and I just flushed the amd64 queue because there were several libthrust test scheduled and we lack the facilities to remove individual tests from the queue. Thanks for using our facilities, but unfortunately we can't support the tests in their current form. Paul [1] https://ci.debian.net/munin/ci-worker13/ci-worker13/index.html [2] https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libthrust/22073748/log.gz
