[oe-commits] [bitbake] branch master updated: runqueue.py: Fix a virtual class extension stamps issue

[git at git.openembedded.org]

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

rpurdie pushed a commit to branch master
in repository bitbake.

The following commit(s) were added to refs/heads/master by this push:
     new da37bda  runqueue.py: Fix a virtual class extension stamps issue
da37bda is described below

commit da37bdad46e11e7ce93ba7a59d58757b769dc16b
Author: Ming Liu <liu.ming50 at gmail.com>
AuthorDate: Fri Jun 29 17:43:23 2018 +0200

    runqueue.py: Fix a virtual class extension stamps issue
    
    The file_name parameter passed to bb.parse.siggen.invalidate_task
    should be a virtual file name instead of a real file name, or else you
    will encounter a following error, for instance, when you run:
    
    $ bitbake nativesdk-lzip -c unpack -f
    
    the error arise:
    | ERROR: An uncaught exception occurred in runqueue
    | if file_name:
    |    > taintfn = d.stamp[file_name] + '.' + task + '.taint'
    | else:
    | KeyError: 'virtual:nativesdk:/opt/poky/meta/recipes-extended/lzip/lzip_1.19.bb'
    
    when multilib builds are used on OE.
    
    Signed-off-by: Ming Liu <liu.ming50 at gmail.com>
    Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
---
 lib/bb/runqueue.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py
index 2d9e18d..0a4d155 100644
--- a/lib/bb/runqueue.py
+++ b/lib/bb/runqueue.py
@@ -1093,7 +1093,7 @@ class RunQueueData:
                     bb.debug(1, "Task %s is marked nostamp, cannot invalidate this task" % taskname)
             else:
                 logger.verbose("Invalidate task %s, %s", taskname, fn)
-                bb.parse.siggen.invalidate_task(taskname, self.dataCaches[mc], fn)
+                bb.parse.siggen.invalidate_task(taskname, self.dataCaches[mc], taskfn)
 
         self.init_progress_reporter.next_stage()
 

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