From: Patrick Ohly <patrick.ohly@intel.com>
To: bitbake-devel@lists.openembedded.org,
Ross Burton <ross.burton@intel.com>
Subject: Re: [PATCH v2 3/3] runqueue.py: revised completion scheduler
Date: Tue, 17 Jan 2017 16:18:24 +0100 [thread overview]
Message-ID: <1484666304.19478.63.camel@intel.com> (raw)
In-Reply-To: <8f61859759b1fe66f1e649ff341582bc51c93161.1484318890.git-series.patrick.ohly@intel.com>
On Fri, 2017-01-13 at 15:51 +0100, Patrick Ohly wrote:
> diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py
> index 48c6a79..0c4f286 100644
> --- a/lib/bb/runqueue.py
> +++ b/lib/bb/runqueue.py
> @@ -183,6 +183,18 @@ class RunQueueScheduler(object):
[...]
> + super(RunQueueSchedulerRmwork, self).__init__(runqueue, rqdata)
The new line must be instead:
super(RunQueueSchedulerCompletion, self).__init__(runqueue, rqdata)
Obviously I haven't tested enough after renaming the scheduler :-/
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-01-17 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 14:51 [PATCH v2 0/3] bitbake: rm_work enhancements Patrick Ohly
2017-01-13 14:51 ` [PATCH v2 1/3] event/ast: Add RecipeTaskPreProcess event before task finalisation Patrick Ohly
2017-01-13 14:51 ` [PATCH v2 2/3] build.py: add preceedtask() API Patrick Ohly
2017-01-13 14:51 ` [PATCH v2 3/3] runqueue.py: revised completion scheduler Patrick Ohly
2017-01-17 15:18 ` Patrick Ohly [this message]
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=1484666304.19478.63.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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