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
