[09:34] https://autopkgtest.ubuntu.com/packages/r/rust-gst-plugin-gtk4/oracular/arm64 please have a look, why do these tests don't time out? [09:55] 719a10be-05ea-47d8-9501-f8d39a942f55 is still running, last output line is about one hour ago [10:01] for e471740e-23a7-4666-bdc1-e90d43c5cc42, it's about the same, and the last line is a long `cargo` command. Building rust is long, and I see in those logs some gaps of almost two hours, like one line starting with 88550s and the next one with 95388s [10:03] If you look at the difference between the `Running for` time and the `starting date and time`, you'll see that the job has actually faced some issue that were judged as "infra issue", and retried right away, thus explaining the difference. This can happen up to three time before the result is pushed anyway for a developer to look at it. [10:04] doko: ^^^ [10:23] ta