On Thursday, May 8, 2025 11:31:41 PM Mountain Standard Time Paul Gevers wrote:
> An alternative that can be done now: the timeout of 2:47h is per test
> stanza in d/t/control (see autopkgtest(1). For some test suites it's not
> hard to split the test suite over multiple stanza. The overal timeout
Hi,
On 09-05-2025 03:28, Soren Stoutner wrote:
On Thursday, May 8, 2025 4:41:16 PM Mountain Standard Time Antonio Terceiro
wrote:
We could allow longer timeouts on a per-package basis and on maintainer
request, like we handle having packages tested with KVM instead of
containers.
This would ne
On Thursday, May 8, 2025 4:41:16 PM Mountain Standard Time Antonio Terceiro
wrote:
> We could allow longer timeouts on a per-package basis and on maintainer
> request, like we handle having packages tested with KVM instead of
> containers.
>
> This would need the code to actually support this to
On Thu, May 08, 2025 at 11:38:35AM -0700, Soren Stoutner wrote:
> I have two questions.
>
> 1. Is there a way to override the 3 hour time limit for Debian CI for a
> particular package?
No.
> 2. Would there be objections to reconsidering the 3 hour default time limit
> for all packages?
We
Every once in a while there is a package that requires more than three hours
to run autopkgtest. One example is pyinstaller-hooks-contrib.
https://tracker.debian.org/pkg/pyinstaller-hooks-contrib
On amd64, armhf, and i386, the tests currently take slightly less than 3
hours. But on arm64, the
5 matches
Mail list logo
