Bug#970606: [Openjdk] Bug#970606: src:openjdk-*: autopkgtest times out on Debian/Ubuntu infrastructure
Hi Matthias, On 21-09-2020 17:52, Paul Gevers wrote: >> Apparently >> the very same tests don't time out on the buildds. > > I don't know what timeouts apply to buildds, but indeed I think they are > much higher to cope with *building* some extremely big packages. Do you know how much time these tests would take? If so, I wonder if we should make it possible for individual packages to have a longer timeout. It would be work on the debci/ci.d.n side of things, but not impossible of course. Paul signature.asc Description: OpenPGP digital signature
Bug#970606: [Openjdk] Bug#970606: src:openjdk-*: autopkgtest times out on Debian/Ubuntu infrastructure
Hi Matthias, On 21-09-2020 11:43, Matthias Klose wrote: > 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. $(man autopkgtest) has a section about timeouts. The defaults apply to the Debian infrastructure and I think to the Ubuntu infrastructure as well: """ There are five timeouts affected by five values of which: short: supposedly short operations like setting up the testbed's apt and checking the state (default: 100s); install: installation of packages including dependencies (default: 3,000s); test: test runs (default: 10,000s); copy: copy files/directories between host and testbed (default: 300s); and build: builds (default: 100,000s). """ > I think it would help to document > these constraints (and yes, Ubuntu doesn't document those either). Where are you missing the info? I'll happily file bugs to request inclusion of the information. > Apparently > the very same tests don't time out on the buildds. I don't know what timeouts apply to buildds, but indeed I think they are much higher to cope with *building* some extremely big packages. > Unsure if you want to track that under the release.d.o meta issue. Don't think there is anything to do there, unless you consider that a place where documentation is missing. Paul signature.asc Description: OpenPGP digital signature
Bug#970606: [Openjdk] Bug#970606: src:openjdk-*: autopkgtest times out on Debian/Ubuntu infrastructure
Control: clone -1 -2 Control: reassign -2 release.debian.org On 9/19/20 9:16 PM, Paul Gevers wrote: > Source: openjdk-15 > Version: 15+36-1 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: timeout > > 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...@lists.debian.org or on #debci. 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
