From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 7/7] gitlab: force ccache to validate compiler version
Date: Wed, 4 Dec 2024 19:48:07 +0000 [thread overview]
Message-ID: <20241204194807.1472261-8-berrange@redhat.com> (raw)
In-Reply-To: <20241204194807.1472261-1-berrange@redhat.com>
By default ccache checks the compiler 'mtime' to determine if it should
invalidate the cache. On FreeBSD the 'mtime' reflects when the compiler
package was installed, rather than when it was built. IOW, on throwaway
CI VMs, the 'mtime' changes on every single job and is thus useless.
It could validate the compiler binary content, but validating the
compiler version string is less CPU intensive.
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
---
.gitlab-ci.d/cirrus/build.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitlab-ci.d/cirrus/build.yml b/.gitlab-ci.d/cirrus/build.yml
index 5c86278bf8..8268e9e547 100644
--- a/.gitlab-ci.d/cirrus/build.yml
+++ b/.gitlab-ci.d/cirrus/build.yml
@@ -34,6 +34,7 @@ build_task:
- export CCACHE_BASEDIR="$(pwd)"
- export CCACHE_DIR="$CCACHE_BASEDIR/ccache"
- export CCACHE_MAXSIZE="1000M"
+ - export CCACHE_COMPILERCHECK="string:$(clang -v 2>&1)"
- ccache --zero-stats
- ccache --show-stats
- mkdir build
--
2.46.0
next prev parent reply other threads:[~2024-12-04 19:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 19:48 [PATCH 0/7] RFC: gitlab: enable use of ccache in FreeBSD / macOS Cirrus CI jobs Daniel P. Berrangé
2024-12-04 19:48 ` [PATCH 1/7] gitlab: don't fail cirrus CI jobs when credits are exhausted Daniel P. Berrangé
2024-12-05 8:38 ` Thomas Huth
2024-12-04 19:48 ` [PATCH 2/7] gitlab: use new(ish) cirrus-vars command for creating config Daniel P. Berrangé
2024-12-04 19:48 ` [PATCH 3/7] gitlab: clean packages in cirrus tasks Daniel P. Berrangé
2024-12-05 8:58 ` Thomas Huth
2024-12-05 9:19 ` Daniel P. Berrangé
2024-12-05 10:09 ` Thomas Huth
2024-12-05 11:00 ` Daniel P. Berrangé
2024-12-04 19:48 ` [PATCH 4/7] gitlab: purge build files from cirrus CI jobs Daniel P. Berrangé
2024-12-04 20:29 ` Philippe Mathieu-Daudé
2024-12-05 10:55 ` Thomas Huth
2024-12-05 11:01 ` Daniel P. Berrangé
2024-12-04 19:48 ` [PATCH 5/7] gitlab: enable ccache with Cirrus CI Daniel P. Berrangé
2024-12-05 10:58 ` Thomas Huth
2024-12-04 19:48 ` [PATCH 6/7] tests: update libvirt-ci submodule for newer ccache Daniel P. Berrangé
2024-12-04 19:48 ` Daniel P. Berrangé [this message]
2024-12-04 20:30 ` [PATCH 7/7] gitlab: force ccache to validate compiler version Philippe Mathieu-Daudé
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=20241204194807.1472261-8-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.