From: Thomas Huth <thuth@redhat.com>
To: Camilla Conte <cconte@redhat.com>, qemu-devel@nongnu.org
Cc: "Eldon Stegall" <eldon-qemu@eldondev.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 2/2] Raise crash-test-debian timeout to 90 minutes
Date: Tue, 11 Apr 2023 10:22:51 +0200 [thread overview]
Message-ID: <9bc1b9c3-a54c-8a59-5b68-af8d63037142@redhat.com> (raw)
In-Reply-To: <20230407145252.32955-2-cconte@redhat.com>
On 07/04/2023 16.52, Camilla Conte wrote:
> When running on the Kubernetes runner, this CI job is timing out.
> Raise the limit to give the job enough time to run.
>
> Signed-off-by: Camilla Conte <cconte@redhat.com>
> ---
> .gitlab-ci.d/buildtest.yml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index ba6f551752..893f8c69b4 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -98,6 +98,7 @@ crash-test-debian:
> needs:
> - job: build-system-debian
> artifacts: true
> + timeout: 90m
> variables:
> IMAGE: debian-amd64
> script:
Eldon recently discovered that the crash-test-debian jobs takes longer on
his runner since it has KVM enabled and the job tests the devices twice -
once with TCG and once with KVM. I assume this is the case for the
Kubernetes runner, too? ... we should likely add a switch to the
device-crash-test script to provide a way to enforce running with one
accelerator only, so we can keep the run time in a sane limit.
Anyway, for the time being, this patch is of course a fair work-around, thus:
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-04-11 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 14:52 [PATCH 1/2] Add CI configuration for Kubernetes Camilla Conte
2023-04-07 14:52 ` [PATCH 2/2] Raise crash-test-debian timeout to 90 minutes Camilla Conte
2023-04-11 8:22 ` Thomas Huth [this message]
2023-05-19 10:23 ` Daniel P. Berrangé
2023-05-19 9:00 ` [PATCH 1/2] Add CI configuration for Kubernetes Daniel P. Berrangé
2023-05-19 12:33 ` Camilla Conte
2023-05-19 12:51 ` Daniel P. Berrangé
2023-05-19 14:06 ` Camilla Conte
2023-05-19 14:15 ` 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=9bc1b9c3-a54c-8a59-5b68-af8d63037142@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cconte@redhat.com \
--cc=eldon-qemu@eldondev.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).