I've compared older good and newer runs that timeout.
$ for i in good.hirsute-amd64.*; do printf "\n\n$i\n"; grep '^autopkgtest .* test .*: - - - - - - - - - - results' $i; done
We see that good cases need ~110-130 minutes to complete "test boot-smoke" and then another 4-12 minutes to complete "test systemd-fsckd".
But the bad cases often take ~210 +/- 10 minutes to reach "test boot-smoke" completion.
But OTOH there are also a few cases needing only the old ~2h to get there (bad.hirsute-amd64.23 / bad.hirsute-amd64.24) - those still hang and eventually fail.
With some ugly awk magic I derived those times for the steps (attached here)
I've compared older good and newer runs that timeout.
$ for i in good.hirsute- amd64.* ; do printf "\n\n$i\n"; grep '^autopkgtest .* test .*: - - - - - - - - - - results' $i; done
We see that good cases need ~110-130 minutes to complete "test boot-smoke" and then another 4-12 minutes to complete "test systemd-fsckd".
But the bad cases often take ~210 +/- 10 minutes to reach "test boot-smoke" completion.
But OTOH there are also a few cases needing only the old ~2h to get there (bad.hirsute- amd64.23 / bad.hirsute- amd64.24) - those still hang and eventually fail.
With some ugly awk magic I derived those times for the steps (attached here)