[oe-commits] [bitbake] 01/02: siggen: Fix hashequiv bug where new hash wasn't referenced correctly

[git at git.openembedded.org]

This is an automated email from the git hooks/post-receive script.

rpurdie pushed a commit to branch master-next
in repository bitbake.

commit 9dc5178f56ab8ae37e1a646c09117c503e48d072
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
AuthorDate: Mon Nov 25 17:18:32 2019 +0000

    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.
    
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 lib/bb/siggen.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/bb/siggen.py b/lib/bb/siggen.py
index a4bb1ff..e19812b 100644
--- a/lib/bb/siggen.py
+++ b/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:

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.