git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org,  Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] ci: update FreeBSD cirrus job
Date: Wed, 31 Jan 2024 14:35:17 -0800	[thread overview]
Message-ID: <xmqq4jet3zdm.fsf@gitster.g> (raw)
In-Reply-To: <20240131191325.33228-1-carenas@gmail.com> ("Carlo Marcelo Arenas Belón"'s message of "Wed, 31 Jan 2024 11:13:25 -0800")

Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:

> FreeBSD 12 is EOL and no longer available, causing errors in this job.
>
> Upgrade to 13.2, which is the next oldest release with support and that
> should keep it for at least another 4 months.
>
> This will be upgraded again once 13.3 is released to avoid furtheer
> surprises.

Thanks.

> "Not enough compute credits to prioritize tasks!" seems to be just a
> reminder that the credit allocate for the Free Tier by Cirrus is all
> used up and which might result in additional delays getting a result.

This statement does not quite help future readers of "git log",
unless they still remember that it was how Dscho noticed the
problem.  Either moving it under "---" line (meaning: remove from
the proposed log message), or adding reference to the original
report, would be more appropriate.  For now, I'd amend the log
message to read:

  The original report [*] of this problem mentions an error message
  "Not enough compute credits to prioritize tasks!".  It seems to be
  just a reminder that the credit allocate for the Free Tier by
  Cirrus is all used up and which might result in additional delays
  getting a result.

  [*] https://lore.kernel.org/git/d2d7da84-e2a3-a7b2-3f95-c8d53ad4dd5f@gmx.de/

or something like that while queuing.

Thanks.

>
> Signed-off-by: Carlo Marcelo Arenas Belón <carenas@gmail.com>
> ---
>  .cirrus.yml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/.cirrus.yml b/.cirrus.yml
> index b6280692d2..77346a4929 100644
> --- a/.cirrus.yml
> +++ b/.cirrus.yml
> @@ -1,7 +1,7 @@
>  env:
>    CIRRUS_CLONE_DEPTH: 1
>  
> -freebsd_12_task:
> +freebsd_task:
>    env:
>      GIT_PROVE_OPTS: "--timer --jobs 10"
>      GIT_TEST_OPTS: "--no-chain-lint --no-bin-wrappers"
> @@ -9,7 +9,7 @@ freebsd_12_task:
>      DEFAULT_TEST_TARGET: prove
>      DEVELOPER: 1
>    freebsd_instance:
> -    image_family: freebsd-12-3
> +    image_family: freebsd-13-2
>      memory: 2G
>    install_script:
>      pkg install -y gettext gmake perl5

  reply	other threads:[~2024-01-31 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 19:13 [PATCH] ci: update FreeBSD cirrus job Carlo Marcelo Arenas Belón
2024-01-31 22:35 ` Junio C Hamano [this message]
2024-01-31 22:57 ` Junio C Hamano

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=xmqq4jet3zdm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.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).