Re: bitbake-worker: where the data come from in handle_runtask?

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2017-03-03 at 16:41 +0800, Du Dengke wrote:
> In file bitbake-worker, the function handle_runtask:
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> fn, task, taskname, quieterrors, appends, taskdepdata, dry_run_exec =
> pickle.loads(data)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> why the "pickle.loads(data)" return 7 results, before this commit:
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 58f08429 (Paul Eggleton      2016-12-16 07:09:13 +1300 428)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> it returns 6 results:
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> fn, task, taskname, quieterrors, appends, taskdepdata =
> pickle.loads(data)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> where the data come from, I want to forcus on the taskdepdata.

In the commit you mention, you'll see this piece:

-                self.rq.worker[mc].process.stdin.write(b"<runtask>" + pickle.dumps((taskfn, task, taskname, False, self.cooker.collection.get_file_appends(taskfn), taskdepdata)) + b"</runtask>")
+                self.rq.worker[mc].process.stdin.write(b"<runtask>" + pickle.dumps((taskfn, task, taskname, False, self.cooker.collection.get_file_appends(taskfn), taskdepdata, self.rqdata.setscene_enforce)) + b"</runtask>")

This is the change which means "data" now has seven elements instead of
six since self.rqdata.setscene_enforce was added.

Cheers,

Richard