summaryrefslogtreecommitdiffstats
path: root/bitbake/LICENSE
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2016-11-02 15:06:50 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-11-16 10:37:58 +0000
commitf17446b645f3f12f804c3920fcb8458698463ab4 (patch)
tree66b916c74ceacb0e56e02d500a243a7432bb52e6 /bitbake/LICENSE
parentaea27a0554961f7be352473a264659458f48c699 (diff)
downloadpoky-f17446b645f3f12f804c3920fcb8458698463ab4.tar.gz
bitbake: siggen: Pass basehash to worker processes and sanity check reparsing result
Bitbake can parse metadata in the cooker and in the worker during builds. If the metadata isn't deterministic, it can change between these two parses and this confuses things a lot. It turns out to be hard to debug these issues currently. This patch ensures the basehashes from the original parsing are passed into the workers and that these are checked when reparsing for consistency. The user is shown an error message if inconsistencies are found. There is debug code in siggen.py (see the "Slow but can be useful for debugging mismatched basehashes" commented code), we don't enable this by default due to performance issues. If you run into this message, enable this code and you will find "sigbasedata" files in tmp/stamps which should correspond to the hashes shown in this error message. bitbake-diffsigs on the files should show which variables are changing. (Bitbake rev: 46207262ee6cdd2e49c4765481a6a24702ca4843) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/LICENSE')
0 files changed, 0 insertions, 0 deletions