From 456f5e0d2325c24bcd51fc8d8fffb415d7cbc3a8 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Mon, 25 Nov 2019 17:18:32 +0000 Subject: bitbake: siggen: Fix hashequiv bug where new hash wasn't referenced correctly If a hash is reported to the hash server, the stamp written out by the current task didn't account for any new hash the server may have provided. Fix this so the correct stamp is written. This means "bitbake X; bitbake X" no longer rebuilds lots of things when hashequiv is active. (Bitbake rev: 4299afdd290f9d1c5616598f5fe83c195a64b63c) Signed-off-by: Richard Purdie --- bitbake/lib/bb/siggen.py | 1 + 1 file changed, 1 insertion(+) (limited to 'bitbake') diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py index a4bb1ff7fb..e19812b17c 100644 --- a/bitbake/lib/bb/siggen.py +++ b/bitbake/lib/bb/siggen.py @@ -508,6 +508,7 @@ class SignatureGeneratorUniHashMixIn(object): if new_unihash != unihash: bb.debug(1, 'Task %s unihash changed %s -> %s by server %s' % (taskhash, unihash, new_unihash, self.server)) bb.event.fire(bb.runqueue.taskUniHashUpdate(fn + ':do_' + task, new_unihash), d) + self.set_unihash(tid, new_unihash) else: bb.debug(1, 'Reported task %s as unihash %s to %s' % (taskhash, unihash, self.server)) except hashserv.client.HashConnectionError as e: -- cgit v1.2.3-54-g00ecf