The cross-i686-tci job is flaky again, with persistent intermittent
failures due to jobs timing out.
https://gitlab.com/qemu-project/qemu/-/issues/2285 has the details
with links to 8 CI jobs in the last week or so with timeouts, typically
something like:
16/258 qemu:qtest+qtest-aarch64 / qtest-aarch64/test-hmp
TIMEOUT 240.17s killed by signal 15 SIGTERM
73/258 qemu:qtest+qtest-ppc / qtest-ppc/boot-serial-test
TIMEOUT 360.14s killed by signal 15 SIGTERM
78/258 qemu:qtest+qtest-i386 / qtest-i386/ide-test
TIMEOUT 60.09s killed by signal 15 SIGTERM
253/258 qemu:softfloat+softfloat-ops / fp-test-mul
TIMEOUT 30.11s killed by signal 15 SIGTERM
254/258 qemu:softfloat+softfloat-ops / fp-test-div
TIMEOUT 30.25s killed by signal 15 SIGTERM
255/258 qemu:qtest+qtest-aarch64 / qtest-aarch64/migration-test
TIMEOUT 480.23s killed by signal 15 SIGTERM
257/258 qemu:qtest+qtest-aarch64 / qtest-aarch64/bios-tables-test
TIMEOUT 610.10s killed by signal 15 SIGTERM
but not always those exact tests. This isn't the first time
this CI job for TCI has been flaky either.
Some of these timeouts are very high -- no test should be taking
10 minutes, even given TCI and a slowish CI runner -- which suggests
to me that there's some kind of intermittent deadlock going on.
Can somebody who cares about TCI investigate, please, and track
down whatever this is?
(My alternate suggestion is that we mark TCI as deprecated in 9.1
and drop it entirely, if nobody cares enough about it...)
thanks
-- PMM
