All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jon Mason" <jdmason@kudzu.us>
To: Ross Burton <ross@burtonini.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH] CI: don't retry jobs
Date: Thu, 14 Jan 2021 14:24:22 -0500	[thread overview]
Message-ID: <20210114192422.GH511@kudzu.us> (raw)
In-Reply-To: <20210112212027.594670-1-ross.burton@arm.com>

On Tue, Jan 12, 2021 at 09:20:27PM +0000, Ross Burton wrote:
> We can't retry jobs blindly because if a build fails with warnings we want
> to fail the job.  With retries enabled the job fails, but is immediately
> retried and builds quickly from sstate without any warnings.
> 
> Thus, all and any warnings are hidden.
> 
> Disabling retries. We may get occasional failures from Docker, we'll have
> to see how bad they are.
> 
> Change-Id: Ib726f14a264c029fdf372fc1b8a02aca52bf5e4c
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---

Pulled into master.

Thanks,
Jon

>  .gitlab-ci.yml | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 3ae0aa3..18f9ae1 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -8,8 +8,6 @@ stages:
>  
>  # Common job fragment to get a worker ready
>  .setup:
> -  # Retry because the runner is flakey (see https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2890)
> -  retry: 2
>    stage: build
>    variables:
>      KAS_WORK_DIR: $CI_PROJECT_DIR/work
> -- 
> 2.25.1
> 

> 
> 
> 


      reply	other threads:[~2021-01-14 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 21:20 [PATCH] CI: don't retry jobs Ross Burton
2021-01-14 19:24 ` Jon Mason [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=20210114192422.GH511@kudzu.us \
    --to=jdmason@kudzu.us \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=ross@burtonini.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.