[oe-commits] [bitbake] 03/03: runqueue: Ensure setscene tasks that aren't covered get built

git at git.openembedded.org git at git.openembedded.org
Fri Sep 7 16:49:35 UTC 2018


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

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

commit f521fc00b0df42e29dfb865254b04f87f5ef567c
Author: Richard Purdie <richard.purdie at linuxfoundation.org>
AuthorDate: Fri Sep 7 17:41:27 2018 +0100

    runqueue: Ensure setscene tasks that aren't covered get built
    
    Running "bitbake gconf-native -c cleansstate; bitbake core-image-sato:do_populate_sdk"
    
    results in a build where it fails to find gconf-native and fails to build it,
    merrily trying to build the SDK without gconf being present.
    
    The issue is the missing setscene tasks are effectively ignored as the later
    code in runqueue thinks that since other sstate tasks are present, these
    'cover' the missing one. In reality we need to call BB_SETSCENE_DEPVALID
    to make that decision. To do that we need a "reduced" setscene dependency
    graph which we don't have in main task graph context.
    
    Since that was already done in setscene, we should just assume anything
    in the non-covered list needs to be built.
    
    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 91911af..d2e248b 100644
--- a/lib/bb/runqueue.py
+++ b/lib/bb/runqueue.py
@@ -1831,7 +1831,7 @@ class RunQueueExecuteTasks(RunQueueExecute):
             bb.build.del_stamp(taskname, self.rqdata.dataCaches[mc], taskfn)
             self.rq.scenequeue_covered.remove(tid)
 
-        toremove = covered_remove
+        toremove = covered_remove | self.rq.scenequeue_notcovered
         for task in toremove:
             logger.debug(1, 'Not skipping task %s due to setsceneverify', task)
         while toremove:

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


More information about the Openembedded-commits mailing list