|author||Zac Medico <email@example.com>||2012-06-24 08:18:12 (GMT)|
|committer||Zac Medico <firstname.lastname@example.org>||2012-06-24 08:18:12 (GMT)|
|parent||test_slot_abi: fix atom == type (diff)|
PollScheduler: schedule inside loop if max_load
This will fix a case like that reported in bug #403895, triggered when the --load-average option is used.
1 files changed, 10 insertions, 3 deletions
diff --git a/pym/_emerge/PollScheduler.py b/pym/_emerge/PollScheduler.py
index 965dc20..5103e31 100644
@@ -148,15 +148,22 @@ class PollScheduler(object):
term_check_id = self.sched_iface.idle_add(self._termination_check)
- # Populate initial event sources. We only need to do
- # this once here, since it can be called during the
- # loop from within event handlers.
+ # Populate initial event sources. Unless we're scheduling
+ # based on load average, we only need to do this once
+ # here, since it can be called during the loop from within
+ # event handlers.
+ max_load = self._max_load
# Loop while there are jobs to be scheduled.
+ if max_load is not None:
+ # We have to schedule periodically, in case the load
+ # average has changed since the last call.
# Clean shutdown of previously scheduled jobs. In the
# case of termination, this allows for basic cleanup
# such as flushing of buffered output to logs.