qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	"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: Wed, 08 Jun 2022 15:59:58 +0100	[thread overview]
Message-ID: <87edzztd3i.fsf@linaro.org> (raw)
In-Reply-To: <20220603124809.70794-1-thuth@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> 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)
>
>  .gitlab-ci.d/buildtest.yml | 22 ++++++++++------------
>  1 file changed, 10 insertions(+), 12 deletions(-)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index ecac3ec50c..baaa0ebb87 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -355,16 +355,15 @@ build-cfi-aarch64:
>        --enable-safe-stack --enable-slirp=git
>      TARGETS: aarch64-softmmu
>      MAKE_CHECK_ARGS: check-build
> -  timeout: 70m
> -  artifacts:
> -    expire_in: 2 days
> -    paths:
> -      - build
> -  variables:
>      # FIXME: This job is often failing, likely due to out-of-memory problems in
>      # the constrained containers of the shared runners. Thus this is marked as
>      # skipped until the situation has been solved.
>      QEMU_JOB_SKIPPED: 1
> +  timeout: 90m
> +  artifacts:
> +    expire_in: 2 days
> +    paths:
> +      - build
>  
>  check-cfi-aarch64:
>    extends: .native_test_job_template
> @@ -396,16 +395,15 @@ build-cfi-ppc64-s390x:
>        --enable-safe-stack --enable-slirp=git
>      TARGETS: ppc64-softmmu s390x-softmmu
>      MAKE_CHECK_ARGS: check-build
> -  timeout: 70m
> -  artifacts:
> -    expire_in: 2 days
> -    paths:
> -      - build
> -  variables:
>      # FIXME: This job is often failing, likely due to out-of-memory problems in
>      # the constrained containers of the shared runners. Thus this is marked as
>      # skipped until the situation has been solved.
>      QEMU_JOB_SKIPPED: 1
> +  timeout: 80m
> +  artifacts:
> +    expire_in: 2 days
> +    paths:
> +      - build
>  
>  check-cfi-ppc64-s390x:
>    extends: .native_test_job_template

Queued to testing/next, thanks.

-- 
Alex Bennée


      parent reply	other threads:[~2022-06-08 15:19 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
2022-06-03 16:32   ` Thomas Huth
2022-06-08 14:59 ` Alex Bennée [this message]

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=87edzztd3i.fsf@linaro.org \
    --to=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).