After the recent changes in bitbake to runqueue, we need to recheck sstate
validity,
particularly in multiconfig builds where tasks have the same checksum.
Avoid printing summary messages in this case. Also avoid multiple events to
toaster
which may not be expecting that at later points in the code.
Signed-off-by: Richard Purdie <richard.pur...@linuxfoundation.org>
---
meta/classes/sstate.bbclass | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 424acfb1557..b604729d84a 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -927,6 +927,10 @@ def sstate_checkhashes(sq_fn, sq_task, sq_hash, sq_hashfn,
d, siginfo=False, *,
bb.event.fire(bb.event.ProcessFinished(msg), d)
+ # Likely checking an individual task hash again for multiconfig sharing of
sstate tasks so skip reporting
+ if len(sq_fn) == 1:
+ return ret
+
inheritlist = d.getVar("INHERIT")
if "toaster" in inheritlist:
evdata = {'missed': [], 'found': []};
--
2.20.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
