summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/runqueue.py
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 /bitbake/lib/bb/runqueue.py
parent5cbf2318b1e8ed1d86ff4b786f6aec66dba8558f (diff)
downloadast2050-yocto-poky-d8ef08c96b12645f44f4c24b3264f2b2ee40161c.zip
ast2050-yocto-poky-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>
Diffstat (limited to 'bitbake/lib/bb/runqueue.py')
-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 6372b65..274ccf2 100644
--- a/bitbake/lib/bb/runqueue.py
+++ b/bitbake/lib/bb/runqueue.py
@@ -139,7 +139,7 @@ class RunQueueScheduler(object):
bestprio = None
for taskid in self.buildable:
prio = self.rev_prio_map[taskid]
- if not bestprio or bestprio > prio:
+ if bestprio is None or bestprio > prio:
stamp = self.stamps[taskid]
if stamp in self.rq.build_stamps.itervalues():
continue
OpenPOWER on IntegriCloud