Hi Paul,
I discussed in private with Sébastien. We are the two main maintainers of
the Octave-related packages. It happens that none of us has enough free
time now to debug the issue.
I suggest that we simply disable the problematic tests, for now. What do
you think?
Best,
Rafael
* Paul Gevers <elb...@debian.org> [2025-01-16 11:42]:
Hi Sébastien
On 14-01-2025 11:13, Sébastien Villemot wrote:
At this stage I still don’t understand the problem. On my local machine
(a recent desktop amd64), the autopkgtest only takes about 90s.
Upstream has no clue either.
I can offer you access to a testbed on our infrastructure. If so,
please connect to me on IRC on #debci; either me or terceiro needs to
be on-line while you're debugging.
By the way, do you know why the debCI runner times out at about 10000s,
while --timeout=36000 was passed to the autopkgtest command?
autopkgtest has multiple timeouts, please see autopkgtest(1). The
--timeout option defines the *global* timeout. However, individual
tests (per d/t/control stanza) are controlled by --timeout-test, which
by default is 10000 s.
Paul
