From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Stefan Weil <sw@weilnetz.de>,
Richard Henderson <richard.henderson@linaro.org>
Subject: cross-i686-tci CI job is flaky again (timeouts): can somebody who cares about TCI investigate?
Date: Tue, 16 Apr 2024 13:10:30 +0100 [thread overview]
Message-ID: <CAFEAcA92aivDF-LjSrtZH6o4UtgrtcWnM2wuPZA5VOiN6j7KMA@mail.gmail.com> (raw)
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
next reply other threads:[~2024-04-16 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:10 Peter Maydell [this message]
2024-04-16 12:17 ` cross-i686-tci CI job is flaky again (timeouts): can somebody who cares about TCI investigate? Stefan Weil via
2024-04-20 20:25 ` Stefan Weil via
2024-04-24 16:27 ` Timeouts in CI jobs (was: cross-i686-tci CI job is flaky again (timeouts): can somebody who cares about TCI investigate?) Stefan Weil via
2024-04-24 17:09 ` Daniel P. Berrangé
2024-04-24 18:10 ` Timeouts in CI jobs Stefan Weil via
2024-04-25 13:27 ` Daniel P. Berrangé
2024-04-25 13:30 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFEAcA92aivDF-LjSrtZH6o4UtgrtcWnM2wuPZA5VOiN6j7KMA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).