From: Richard Henderson <richard.henderson@linaro.org>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Daniel P . Berrange" <berrange@redhat.com>
Cc: Wainer dos Santos Moschetta <wainersm@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [PATCH] gitlab-ci: Fix the build-cfi-aarch64 and build-cfi-ppc64-s390x jobs
Date: Fri, 3 Jun 2022 09:17:03 -0700 [thread overview]
Message-ID: <dabe3016-83a7-e5f9-6ff2-0fb20c7cfb25@linaro.org> (raw)
In-Reply-To: <20220603124809.70794-1-thuth@redhat.com>
On 6/3/22 05:48, Thomas Huth wrote:
> The job definitions recently got a second "variables:" section by
> accident and thus are failing now if one tries to run them. Merge
> the two sections into one again to fix the issue.
>
> And while we're at it, bump the timeout here (70 minutes are currently
> not enough for the aarch64 job). The jobs are marked as manual anyway,
> so if the user starts them, they want to see their result for sure and
> then it's annoying if the job timeouts too early.
>
> Fixes: e312d1fdbb ("gitlab: convert build/container jobs to .base_job_template")
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> I wonder whether we should remove the build-cfi-aarch64 job instead.
> When I tried to run it during the past months, it was always failing
> for me. This time, I tried to bump the timeout while I was at it,
> and it takes longer than 80 minutes here to finish - so I asume
> nobody ever ran this successfully in the last months... Is anybody
> using this job at all? I think if we want to have CFI coverage here,
> it should get replaced by a custom runner job that runs on a more
> beefy machine... (the ppc64-s390x job is fine by the way, it often
> only runs a little bit longer than 60 minutes - I still bumped the
> timeout here, too, just to be on the safe side)
Acked-by: Richard Henderson <richard.henderson@linaro.org>
I think it might be useful to extend the other s390x jobs a bit too. The last couple of
fails have the test *nearly* completing. E.g. your most recent pr:
https://gitlab.com/qemu-project/qemu/-/jobs/2544009687
Whether that indicates we've a speed regression, or host loading, or simply changes to the
testsuite, I don't know.
r~
next prev parent reply other threads:[~2022-06-03 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 12:48 [PATCH] gitlab-ci: Fix the build-cfi-aarch64 and build-cfi-ppc64-s390x jobs Thomas Huth
2022-06-03 16:17 ` Richard Henderson [this message]
2022-06-03 16:32 ` Thomas Huth
2022-06-08 14:59 ` Alex Bennée
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=dabe3016-83a7-e5f9-6ff2-0fb20c7cfb25@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).