linux/poky.git/bitbake/bin, branch yocto-2.2.3

bitbake: bitbake-worker: Handle cooker/worker IO deadlocking

2017-02-03T09:52:19+00:00

I noiced builds where tasks seemed to be taking a surprisingly long time. When I looked at the output of top/pstree, these tasks were no longer running despite being listed in knotty. Some were in D/Z state waiting for their exit code to be collected, others were simply not present at all. strace showed communication problems between the worker and cooker, each was trying to write to the other and nearly deadlocking. Eventually, timeouts would allow them to echange 64kb of data but this was only happening every few seconds. Whilst this particularly affected builds on machines with large numbers of cores (and hence highly parallal task execution) and in cases where I had a lot of debug enabled, this situation is clearly bad in general. This patch introduces a thread to the worker which is used to write data back to cooker. This means that the deadlock can't occur and data flows much more freely and effectively. (Bitbake rev: f48befe1163147b02a9926ee38af0f7258a477e0) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: print full traceback instead of message only

2016-11-16T10:37:58+00:00

Print full traceback instead of just the exception message in the child() function inside fork_off_task(). This makes debugging a lot easier as the function catches a generic "Exception" and the exception message alone might not give much information. [YOCTO #10393] (Bitbake rev: 61cc397a5b7136afb37052a2860c6c39a176ddab) Signed-off-by: Markus Lehtonen Signed-off-by: Richard Purdie

bitbake: bitbake: Update version to 1.32.0

2016-10-11T07:47:17+00:00

(Bitbake rev: d9713ed13d0c88c7ee38e8d7b52aa525318af6e3) Signed-off-by: Richard Purdie

bitbake: bitbake: Update version to 1.31.2

2016-10-05T09:10:11+00:00

(Bitbake rev: 100a0aef3d121d950d89c4152f56957628f2f933) Signed-off-by: Richard Purdie

bitbake: toaster: stop modifying OEROOT in toaster script

2016-09-30T15:52:22+00:00

Setting OEROOT in toaster script makes oe-init-build-env to break with error: bash: ../bitbake/bin/../../scripts/oe-buildenv-internal: No such file or directory This happens because OEROOT contains path relative to build directory. Renamed OEROOT to OE_ROOT and unset it after it's used. (Bitbake rev: 3b0967b160dc6123ef75e6f378221347bd923f1b) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: don't kill all runserver processes

2016-09-07T23:33:47+00:00

Toaster script kills runserver process 2 ways: - sending signal to pid from .toastermain.pid. - sending signal to pids found by grepping ps output: ps fux | grep "python.*manage.py runserver" Second approach is redundant and harmfull as it kills all django development server running on the machine. [YOCTO #7973] (Bitbake rev: 0f47b17fe88dc660648d94b2d8d8286d87ae6295) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: remove handling of .toasterui.pid

2016-09-07T23:33:47+00:00

This file is not created anywhere, but handled in toaster script code. (Bitbake rev: 16f3cd3535c9eec71ea7594c1e3a83db00dba7ca) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: toaster: don't kill toaster on start

2016-09-07T23:33:47+00:00

There is no point of trying to kill django development server when toaster starts because 'manage.py checksocket' command is already used in the script code to check if development server port is occupied. Even if Toaster is listening on another port, killing previous instance looks quite implicit and doesn't solve anything as there are other processes that might be still running. (Bitbake rev: 0dab45e9815e8939219900264e86f569c714b7c6) Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: bitbake-diffsigs/bitbake-layers: Ensure tinfoil is shut down correctly

2016-09-02T17:09:48+00:00

We should always shut down tinfoil when we're finished with it, either by explicitly calling the shutdown() method or by using it as a context manager ("with ..."). (Bitbake rev: 131e6dc4bbd197774d35d2b266bfb0816f6e6b1e) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake-selftest: enable bitbake logging to stdout

2016-08-20T15:08:59+00:00

Now you get the bb logger output for failed tests. This helps debugging problems. Also, all stdout/stderr data for successful tests is silenced which makes for less cluttered console output. (Bitbake rev: ea19972a16f7639f944823d1d8a7728105460136) Signed-off-by: Markus Lehtonen Signed-off-by: Richard Purdie