diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-11-02 15:06:50 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-05-18 13:12:30 +0100 |
commit | c3c14808dc4ff62196ef22bfb4984369e4740647 (patch) | |
tree | 268f29c6433420f4755eef874ad4599bb6b38937 /meta-selftest/recipes-test | |
parent | c60a0a51d778bf25d926aa5c74325a3fe9d73a05 (diff) | |
download | poky-c3c14808dc4ff62196ef22bfb4984369e4740647.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)
(Bitbake rev: aa873f982ae4a56b135abd9eee169794e4c3aadd)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixed up do to python3 changes not being in krogoth.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-selftest/recipes-test')
0 files changed, 0 insertions, 0 deletions