I have two questions.
1. Is there a way to override the 3 hour time limit for Debian CI for a particular package?
2. Would there be objections to reconsidering the 3 hour default time limit for all packages?
I would hate to have to disable autopkgtest for some or all architectures on these packages, as the output has been beneficial. But I also don’t want to
prevent migration to testing just because the tests are timing out.
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 be written first, though. We need to be careful with this to prevent packages with
long-running test suites from causing a DoS on the infrastructure.
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 is 8.5h (except on riscv64 where it's currently doubled).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 84:41:12 |
Calls: | 9,679 |
Files: | 13,722 |
Messages: | 6,173,507 |