From: Henning Schild <henning.schild@siemens.com>
To: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] bitbake-diffsigs: make finding of changed signatures more robust
Date: Wed, 13 Apr 2022 10:19:54 +0200 [thread overview]
Message-ID: <20220413101954.67aca2e0@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220413063534.799526-3-adriaan.schmidt@siemens.com>
Am Wed, 13 Apr 2022 08:35:34 +0200
schrieb Adriaan Schmidt <adriaan.schmidt@siemens.com>:
> In `runtaskhashes`, the keys contain the absolute paths to the
> recipe. When working with shared sstate caches (where these absolute
> paths can be different) we see that compare_sigfiles does not
> identifiy a changed hash of a dependent task as "changed", but
> instead as "removed"&"added", preventing the function from recursing
> and continuing the comparison.
>
> By calling `clean_basepaths` before comparing the `runtaskhashes`
> dicts, we avoid this.
>
> Submitted upstream:
> https://lists.openembedded.org/g/bitbake-devel/message/13603
Submitted does not count, we will have to wait till it is merged and
then we can think about a backport.
How important is that? If it is just "nice to have" i think we should
wait and not even do the backport once merged into bitbake.
Henning
> Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com>
> ---
> bitbake/lib/bb/siggen.py | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py
> index 0d88c6ec..8b23fd04 100644
> --- a/bitbake/lib/bb/siggen.py
> +++ b/bitbake/lib/bb/siggen.py
> @@ -944,8 +944,8 @@ def compare_sigfiles(a, b, recursecb=None,
> color=False, collapsed=False):
>
> if 'runtaskhashes' in a_data and 'runtaskhashes' in b_data:
> - a = a_data['runtaskhashes']
> - b = b_data['runtaskhashes']
> + a = clean_basepaths(a_data['runtaskhashes'])
> + b = clean_basepaths(b_data['runtaskhashes'])
> changed, added, removed = dict_diff(a, b)
> if added:
> for dep in added:
> @@ -956,7 +956,7 @@ def compare_sigfiles(a, b, recursecb=None,
> color=False, collapsed=False): #output.append("Dependency on task %s
> was replaced by %s with same hash" % (dep, bdep)) bdep_found = True
> if not bdep_found:
> -
> output.append(color_format("{color_title}Dependency on task %s was
> added{color_default} with hash %s") % (clean_basepath(dep), b[dep]))
> +
> output.append(color_format("{color_title}Dependency on task %s was
> added{color_default} with hash %s") % (dep, b[dep])) if removed: for
> dep in removed: adep_found = False
> @@ -966,11 +966,11 @@ def compare_sigfiles(a, b, recursecb=None,
> color=False, collapsed=False): #output.append("Dependency on task %s
> was replaced by %s with same hash" % (adep, dep)) adep_found = True
> if not adep_found:
> -
> output.append(color_format("{color_title}Dependency on task %s was
> removed{color_default} with hash %s") % (clean_basepath(dep), a[dep]))
> +
> output.append(color_format("{color_title}Dependency on task %s was
> removed{color_default} with hash %s") % (dep, a[dep])) if changed:
> for dep in changed: if not collapsed:
> - output.append(color_format("{color_title}Hash
> for dependent task %s changed{color_default} from %s to %s") %
> (clean_basepath(dep), a[dep], b[dep]))
> + output.append(color_format("{color_title}Hash
> for dependent task %s changed{color_default} from %s to %s") % (dep,
> a[dep], b[dep])) if callable(recursecb): recout = recursecb(dep,
> a[dep], b[dep]) if recout:
next prev parent reply other threads:[~2022-04-13 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 6:35 [PATCH 0/2] Sstate maintenance script Adriaan Schmidt
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 [this message]
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=20220413101954.67aca2e0@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--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