qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>
Subject: Gitlab CI caching is not working
Date: Thu, 12 Sep 2024 07:38:37 +0200	[thread overview]
Message-ID: <d88511da-de21-4260-bf69-2b68f92a37b9@redhat.com> (raw)


  Hi!

While looking at some recent CI jobs, I noticed that the caching of the 
Gitlab-CI jobs is not working at all anymore. In the build jobs, the ccache 
saving is not working and causing a complete cache miss of each compile:

  https://gitlab.com/qemu-project/qemu/-/jobs/7802183187#L5328

And, maybe more important, in the avocado/functional jobs we don't cache the 
assets anymore, causing a re-download of multiple gigabytes each time:

  https://gitlab.com/qemu-project/qemu/-/jobs/7802183251#L29

(the du -chs in line 35 is not executed, thus the cache is nonexistent)

The problem is not new, it's been there for some weeks already, e.g. here's 
a run from the last freeze period (when the job was only running avocado tests):

  https://gitlab.com/qemu-project/qemu/-/jobs/7753544153#L86

There is a suspicious message at the beginning of the logs:

  "No URL provided, cache will not be downloaded from shared cache server. 
Instead a local version of cache will be extracted."

... but since we use throw-away containers for building, I guess there is no 
local version of the cache?

Anyway, the problem only exists for the k8s runners, in my private clone of 
the repository that uses shared runners from gitlab, the caching is working 
right.

Could somebody please have a look into this? Fixing the caching might speed 
up our build time quite a bit, I think.

  Thomas



             reply	other threads:[~2024-09-12  5:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  5:38 Thomas Huth [this message]
2024-09-12  8:15 ` Gitlab CI caching is not working Daniel P. Berrangé

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=d88511da-de21-4260-bf69-2b68f92a37b9@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@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 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).