summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2014-04-13 11:44:25 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-04-23 11:43:29 +0100
commitd8ef08c96b12645f44f4c24b3264f2b2ee40161c (patch)
tree6d14d07c270491aa7b86fee1c7940d1ca8258b4f
parent5cbf2318b1e8ed1d86ff4b786f6aec66dba8558f (diff)
downloadpoky-d8ef08c96b12645f44f4c24b3264f2b2ee40161c.tar.gz
bitbake: runqueue: Fix handling of zero priority task
The zero priority task should be run first but was being confused with the None value the priority field defaulted to. Check for None explicitly to avoid this error. In the real world this doesn't change much but it confused the debug output from the schedulers. (Bitbake rev: 49c9d8c9400f74c804c2f36462639236e0841ff0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--bitbake/lib/bb/runqueue.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/bitbake/lib/bb/runqueue.py b/bitbake/lib/bb/runqueue.py
index 6372b65fd9..274ccf2673 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -139,7 +139,7 @@ class RunQueueScheduler(object):
139 bestprio = None 139 bestprio = None
140 for taskid in self.buildable: 140 for taskid in self.buildable:
141 prio = self.rev_prio_map[taskid] 141 prio = self.rev_prio_map[taskid]
142 if not bestprio or bestprio > prio: 142 if bestprio is None or bestprio > prio:
143 stamp = self.stamps[taskid] 143 stamp = self.stamps[taskid]
144 if stamp in self.rq.build_stamps.itervalues(): 144 if stamp in self.rq.build_stamps.itervalues():
145 continue 145 continue