On Wed, Aug 10, 2022 at 08:06:29AM +0200, Paul Gevers wrote: > I looked at the results of the autopkgtest of you package because it was > showing up on our page for long running tests on s390x. I noticed that the > test always fails on s390x with an autopkgtest timeout. Your package > regressed on armhf and arm64 around April 2022. > > Regressions in testing on amd64 and arm64 are considered RC by the release > team [1]. Tests that time out and fail while normally running quickly are a > serious burden on our infrastructure, please try to prevent the apparent > hang. > > Don't hesitate to reach out if you need help and some more information > from our infrastructure. > > Paul > > https://ci.debian.net/packages/m/mercurial/testing/amd64/ > > [1] https://release.debian.org/testing/rc_policy.txt (section 6.a)
Unfortunately, this bug report suffers from multiple cut&paste or template error. The ci link points to the mercurial page for amd64, the text alternates between s390s, armhf, arm64 and amd64. I tried the (dead simple) autopkgtest on the s390s and arm64 porterboxes and it succeeded in a second's time. I have sharpened the expression that counts the CPUs in lscpu's output and hope this will fix the issue. I also fixed a syntax error in the test, but that should cause the test to error out and not hang. Can you find out in which line the autopkgtest stalls? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
