From: Anton Mikanovich <amikan@ilbers.de>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/4] Improve cacheability
Date: Wed, 4 May 2022 10:50:18 +0300 [thread overview]
Message-ID: <3b8578d9-089c-b07c-c976-5aa302c90124@ilbers.de> (raw)
In-Reply-To: <20220412120813.467516-1-adriaan.schmidt@siemens.com>
12.04.2022 15:08, Adriaan Schmidt wrote:
> We have recently started analyzing more details on sstate caching, and
> identified some potential optimizations. This mainly concerns cases
> of absolute paths contained in variables that are used as inputs to
> the sstate signature caclulation, which can lead to "false negatives"
> when sstate looks for cache hits, e.g., when CI runs on a different
> runner (with different local workdir).
>
> This series contains independent patches with fixes for some issues
> we found so far.
>
> Changes since v1:
> - fixed typo in p4
>
> Adriaan Schmidt (4):
> bitbake.conf: always start with empty SRC_URI
> bitbake.conf: add isar paths to BB_HASHBASE_WHITELIST
> isar-bootstrap: no absolute paths in SRC_URI
> base.bbclass: don't pass absolute paths to root_cleandirs
>
> meta/classes/base.bbclass | 14 +++++++++-----
> meta/conf/bitbake.conf | 5 +++--
> .../recipes-core/isar-bootstrap/isar-bootstrap.inc | 5 +++--
> 3 files changed, 15 insertions(+), 9 deletions(-)
>
Applied to next, thanks.
prev parent reply other threads:[~2022-05-04 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 12:08 Adriaan Schmidt
2022-04-12 12:08 ` [PATCH v2 1/4] bitbake.conf: always start with empty SRC_URI Adriaan Schmidt
2022-04-12 12:08 ` [PATCH v2 2/4] bitbake.conf: add isar paths to BB_HASHBASE_WHITELIST Adriaan Schmidt
2022-04-12 12:08 ` [PATCH v2 3/4] isar-bootstrap: no absolute paths in SRC_URI Adriaan Schmidt
2022-04-12 12:08 ` [PATCH v2 4/4] base.bbclass: don't pass absolute paths to root_cleandirs Adriaan Schmidt
2022-05-04 7:50 ` Anton Mikanovich [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=3b8578d9-089c-b07c-c976-5aa302c90124@ilbers.de \
--to=amikan@ilbers.de \
--cc=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