Dear maintainers, Matthias,

For a long time, the autopkgtests of openjdk-* have been failing on the
ci.debian.net infrastructure and they are currently blacklisted because
they time out and thus fail. As can be seen on the Ubuntu autopkgtest
framework, this is no different for openjdk-15 [1] and some recent try
outs [2,3] show it's still the case on the Debian infrastructure as
well. Due to the failure/blacklist, openjdk-15 is not migrating to
testing. Can you please fix the autopkgtest to not time out on our
infrastructure?

If you need help investigating the situation on our infrastructure,
don't hesitate to contact us on debian-ci@lists.debian.org or on #debci.

Paul

[1] http://autopkgtest.ubuntu.com/packages/openjdk-15
[2]
https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openjdk-15/7077662/log.gz
[3]
https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openjdk-15/7077661/log.gz

Control: clone -1 -2
Control: reassign -2 release.debian.org

I don't think that referring to the Ubuntu autopkg testers is helping here.  I
couldn't find any documentation on the timeout settings for the Debian
infrastructure, for both amd64 and arm64.  I think it would help to document
these constraints (and yes, Ubuntu doesn't document those either).  Apparently
the very same tests don't time out on the buildds.

Unsure if you want to track that under the release.d.o meta issue.

Matthias

Hi debci co-maintainers,
would be nice if we could have some exceptions for packages where the
tests structurally take longer and the effort to fix/split that is too big.

Paul