From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Yonggang Luo" <luoyonggang@gmail.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: [PATCH] gitlab: purge msys pacman cache
Date: Fri, 10 Oct 2025 19:59:47 +0200 [thread overview]
Message-ID: <9a3e44d1-71c3-4725-965f-a8a3d2eb6736@redhat.com> (raw)
In-Reply-To: <20251010160545.144760-1-berrange@redhat.com>
On 10/10/2025 18.05, Daniel P. Berrangé wrote:
> For the Windows msys2 CI job we install many packages using pacman
> and use the GitLab cache to preserve the pacman cache across CI
> runs. While metadata still needs downloading, this avoids pacman
> re-downloading packages from msys2 if they have not changed.
>
> The problem is that pacman never automatically purges anything
> from its package cache. Thus the GitLab cache is growing without
> bound and packing/unpacking the cache is consuming an increasing
> amount of time in the CI job.
>
> If we run 'pacman -Sc' /after/ installing our desired package set,
> it will purge any cached downloaded packages that are not matching
> any installed package.
>
> This will (currently) cap the pacman download cache at approx
> 256 MB.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/windows.yml | 1 +
> 1 file changed, 1 insertion(+)
>
> See a test job with this change, plus a find across the msys
> pacman cache, showing the cleanup effects....
>
> Before cleanup:
>
> https://gitlab.com/berrange/qemu/-/jobs/11679136531#L34
>
> After cleanup:
>
> https://gitlab.com/berrange/qemu/-/jobs/11679136531#L1126
>
> diff --git a/.gitlab-ci.d/windows.yml b/.gitlab-ci.d/windows.yml
> index 1e6a01bd9a..6e1135d8b8 100644
> --- a/.gitlab-ci.d/windows.yml
> +++ b/.gitlab-ci.d/windows.yml
> @@ -87,6 +87,7 @@ msys2-64bit:
> mingw-w64-x86_64-pkgconf
> mingw-w64-x86_64-python
> mingw-w64-x86_64-zstd"
> + - .\msys64\usr\bin\bash -lc "pacman -Sc --noconfirm"
> - Write-Output "Running build at $(Get-Date -Format u)"
> - $env:JOBS = $(.\msys64\usr\bin\bash -lc nproc)
> - $env:CHERE_INVOKING = 'yes' # Preserve the current working directory
Reviewed-by: Thomas Huth <thuth@redhat.com>
I just tested this with some additional "ls -lR /var/cache/pacman" added,
and it seems to work as expected:
https://gitlab.com/thuth/qemu/-/jobs/11680562487#L293
This just removed an old "mingw-w64-x86_64-python-3.12.11-4-any.pkg.tar.zst"
package, but kept the newer 3.12.12 package (and all other currently
installed packages) around. Thus also:
Tested-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-10-10 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 16:05 [PATCH] gitlab: purge msys pacman cache Daniel P. Berrangé
2025-10-10 17:23 ` Peter Maydell
2025-10-10 17:43 ` Daniel P. Berrangé
2025-10-10 17:59 ` Thomas Huth [this message]
2025-10-12 2:28 ` 罗勇刚(Yonggang Luo)
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=9a3e44d1-71c3-4725-965f-a8a3d2eb6736@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=luoyonggang@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).