git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] sparse: ignore warning from new glibc headers
Date: Tue, 08 Apr 2025 15:35:13 -0700	[thread overview]
Message-ID: <xmqq34eiuvry.fsf@gitster.g> (raw)
In-Reply-To: <77f82414-261c-d2bc-f911-ed3d4b06c86e@gmx.de> (Johannes Schindelin's message of "Tue, 8 Apr 2025 22:56:33 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Due to the brownouts today (see
> https://github.com/actions/runner-images/issues/11101, surfaced e.g. in
> https://github.com/git/git/actions/runs/14342895944/job/40206357016), your
> patch came in handy, as it is required for the following fix:

Good timing ;-)
cf. https://lore.kernel.org/git/xmqqo6x6wgs8.fsf@gitster.g/

>
> -- snipsnap --

Does mailinfo consider this as a scissors line?

> Subject: [PATCH] ci: upgrade `sparse` to supported build agents
>
> The `sparse` job still uses the `ubuntu-20.04` runner pool, but that
> pool is about to go away, so let's stop using it.
>
> There is no `sparse-22.04` artifact provided by the "Build sparse for
> Ubuntu" Azure Pipeline, but that is not necessary anyway because Ubuntu
> 22.04 has the `sparse` package: https://packages.ubuntu.com/jammy/sparse

Perfect.  Will take a look.

Thanks.

> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
> ---
>  .github/workflows/main.yml | 11 +----------
>  ci/install-dependencies.sh |  2 +-
>  2 files changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> index ff44c0a8c067..c9455246269d 100644
> --- a/.github/workflows/main.yml
> +++ b/.github/workflows/main.yml
> @@ -449,20 +449,11 @@ jobs:
>      if: needs.ci-config.outputs.enabled == 'yes'
>      env:
>        jobname: sparse
> -    runs-on: ubuntu-20.04
> +    runs-on: ubuntu-22.04
>      concurrency:
>        group: sparse-${{ github.ref }}
>        cancel-in-progress: ${{ needs.ci-config.outputs.skip_concurrent == 'yes' }}
>      steps:
> -    - name: Download a current `sparse` package
> -      # Ubuntu's `sparse` version is too old for us
> -      uses: git-for-windows/get-azure-pipelines-artifact@v0
> -      with:
> -        repository: git/git
> -        definitionId: 10
> -        artifact: sparse-20.04
> -    - name: Install the current `sparse` package
> -      run: sudo dpkg -i sparse-20.04/sparse_*.deb
>      - uses: actions/checkout@v4
>      - name: Install other dependencies
>        run: ci/install-dependencies.sh
> diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
> index 0df74610d063..8700c0f2924d 100755
> --- a/ci/install-dependencies.sh
> +++ b/ci/install-dependencies.sh
> @@ -119,7 +119,7 @@ StaticAnalysis)
>  sparse)
>  	sudo apt-get -q update -q
>  	sudo apt-get -q -y install libssl-dev libcurl4-openssl-dev \
> -		libexpat-dev gettext zlib1g-dev
> +		libexpat-dev gettext zlib1g-dev sparse
>  	;;
>  Documentation)
>  	sudo apt-get -q update
> --
> 2.49.0.windows.1

      reply	other threads:[~2025-04-08 22:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 23:17 [PATCH] sparse: ignore warning from new glibc headers Đoàn Trần Công Danh
2024-07-17 16:54 ` Junio C Hamano
2024-07-17 18:40   ` Ramsay Jones
2024-07-17 18:51     ` Junio C Hamano
2024-07-17 19:20       ` Ramsay Jones
2024-07-17 22:36         ` Ramsay Jones
2024-07-17 22:53           ` Junio C Hamano
2024-07-18  0:02             ` Ramsay Jones
2024-07-18  2:39               ` Đoàn Trần Công Danh
2024-07-18  7:07                 ` Junio C Hamano
2024-07-18  8:46                 ` Đoàn Trần Công Danh
2024-07-18  4:47               ` Junio C Hamano
2024-07-19  2:03                 ` Ramsay Jones
2025-04-08 20:56 ` Johannes Schindelin
2025-04-08 22:35   ` Junio C Hamano [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=xmqq34eiuvry.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=congdanhqx@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).