summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/pyinotify.py
diff options
context:
space:
mode:
authorSchmidt, Adriaan <adriaan.schmidt@siemens.com>2022-04-12 09:42:57 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-04-14 09:48:33 +0100
commit33b929192e78b09dfb1ea84c76db2eae4ce444a1 (patch)
treefe773ddf94a1e0418f9d108bde2c042c3ddbc178 /bitbake/lib/pyinotify.py
parent73fa855f6af5ef9c3a78656aa56f09d213601be2 (diff)
downloadpoky-33b929192e78b09dfb1ea84c76db2eae4ce444a1.tar.gz
bitbake: bitbake-diffsigs: make finding of changed signatures more robust
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. (Bitbake rev: 7358378b90b68111779e6ae72948e5e7a3de00a9) Signed-off-by: Adriaan Schmidt <adriaan.schmidt@siemens.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/pyinotify.py')
0 files changed, 0 insertions, 0 deletions