From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: SetScene tasks hang forever?
Date: Wed, 09 May 2012 21:32:04 +0100 [thread overview]
Message-ID: <1336595524.2494.77.camel@ted> (raw)
In-Reply-To: <4FAAAEB6.2060703@palm.com>
Hi Rich,
You might like to try the change below as I think it might address the problem.
Cheers,
Richard
bitbake/runqueue: Fix 'full' stamp checking to be more efficient and cache results
This should fix issues where bitbake would seemingly lock up when checking
certain configurations of stampfiles.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index b870caf..48433be 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -875,7 +875,7 @@ class RunQueue:
bb.msg.fatal("RunQueue", "check_stamps fatal internal error")
return current
- def check_stamp_task(self, task, taskname = None, recurse = False):
+ def check_stamp_task(self, task, taskname = None, recurse = False, cache = {}):
def get_timestamp(f):
try:
if not os.access(f, os.F_OK):
@@ -915,6 +915,9 @@ class RunQueue:
t1 = get_timestamp(stampfile)
for dep in self.rqdata.runq_depends[task]:
if iscurrent:
+ if dep in cache:
+ iscurrent = cache[dep]
+ continue
fn2 = self.rqdata.taskData.fn_index[self.rqdata.runq_fnid[dep]]
taskname2 = self.rqdata.runq_task[dep]
stampfile2 = bb.build.stampfile(taskname2, self.rqdata.dataCache, fn2)
@@ -931,7 +934,9 @@ class RunQueue:
logger.debug(2, 'Stampfile %s < %s', stampfile, stampfile2)
iscurrent = False
if recurse and iscurrent:
- iscurrent = self.check_stamp_task(dep, recurse=True)
+ iscurrent = self.check_stamp_task(dep, recurse=True, cache=cache)
+ cache[dep] = iscurrent
+ cache[task] = iscurrent
return iscurrent
def execute_runqueue(self):
next prev parent reply other threads:[~2012-05-09 20:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:21 SetScene tasks hang forever? Rich Pixley
2012-05-02 18:40 ` Mark Hatle
2012-05-02 19:16 ` Rich Pixley
2012-05-02 19:40 ` Mark Hatle
2012-05-02 19:45 ` Rich Pixley
2012-05-02 19:48 ` Mark Hatle
2012-05-02 23:06 ` Richard Purdie
2012-05-06 17:36 ` Rich Pixley
2012-05-07 16:38 ` Rich Pixley
2012-05-08 12:34 ` Richard Purdie
2012-05-09 17:51 ` Rich Pixley
2012-05-09 19:52 ` Richard Purdie
2012-05-09 23:04 ` Rich Pixley
2012-05-09 23:26 ` Richard Purdie
2012-05-10 0:03 ` Rich Pixley
2012-05-09 20:32 ` Richard Purdie [this message]
2012-05-09 23:20 ` Rich Pixley
2012-05-09 23:32 ` Richard Purdie
2012-05-10 0:00 ` Rich Pixley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1336595524.2494.77.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox