From: Adriaan Schmidt <adriaan.schmidt@siemens.com>
To: <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH 0/2] Sstate maintenance script
Date: Wed, 13 Apr 2022 08:35:32 +0200 [thread overview]
Message-ID: <20220413063534.799526-1-adriaan.schmidt@siemens.com> (raw)
Hi,
We have been running CI with shared sstate caches for some months now, in
several downstream projects. This is the cache maintenance script that has
evolved during that time. Detailed documentation is in the script itself.
Main features:
- upload cache artifacts to shared caches on filesystem, http, or s3
- clean old artifacts from shared caches
- analyze in detail why cache misses happen (what has changed in the signatures)
The last one is especially interesting, and has already yielded some
improvements to the cacheability of Isar ([PATCH v2 0/4] Improve cacheability);
analysis is still ongoing.
This feature becomes more robust with a patch to bitbake (p2 of this series,
also submitted upstream).
One issue: testing!
This is not easy, because it involves infrastructure, and artificial tests
that provide decent coverage would be quite complex to design.
If we declare that we sufficiently trust the sstate code, we could add a
shared/persistent cache to the Isar CI infrastructure. This would further test
the sstate feature and all steps involved in maintaining such a setup.
In addition, it would significantly speed up CI builds.
Adriaan
Adriaan Schmidt (2):
scripts: add isar-sstate
bitbake-diffsigs: make finding of changed signatures more robust
bitbake/lib/bb/siggen.py | 10 +-
scripts/isar-sstate | 743 +++++++++++++++++++++++++++++++++++++++
2 files changed, 748 insertions(+), 5 deletions(-)
create mode 100755 scripts/isar-sstate
--
2.30.2
next reply other threads:[~2022-04-13 6:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 6:35 Adriaan Schmidt [this message]
2022-04-13 6:35 ` [PATCH 1/2] scripts: add isar-sstate Adriaan Schmidt
2022-04-14 7:36 ` Henning Schild
2022-04-13 6:35 ` [PATCH 2/2] bitbake-diffsigs: make finding of changed signatures more robust Adriaan Schmidt
2022-04-13 8:19 ` Henning Schild
2022-04-14 8:03 ` Schmidt, Adriaan
2022-04-14 8:22 ` Henning Schild
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=20220413063534.799526-1-adriaan.schmidt@siemens.com \
--to=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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