Hi Jeff, On 27-09-2022 08:17, Jeff wrote:
I also offer to run the test (once or twice) manually and get information out of the testbed, if you tell me the exact commands you want me to run in the testbed.Please trigger a new run. I can't add more diagnostics until I know where.
Done so a couple of times, we'll first need to hit one that times out of course. I'll continue to trigger until we find one for a while.
What bothers me about this is that these flaky tests do not occur with the buildd hosts:https://buildd.debian.org/status/logs.php?pkg=gscan2pdf&arch=all The only failure took 7 minutes, not 27 hours. So how do the CI hosts diff from the buildd ones?
I don't know how buildd's look like, but an obvious delta is that autopkgtests on our host run inside lxc. Also, as your package is arch:all only, it always runs on amd64. I think one of the delta's we have for *several* hosts is that the amount of cores and RAM available for the test is significantly higher than on buildds. On a lot of our hosts, we also run multiple debci workers in parallel, so timing wise, you may be seeing varying performance even on the same host.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
