linux/poky.git/bitbake/bin, branch dizzy-12.0.1

bitbake: bitbake-worker: exit normally when SIGHUP

2014-12-31T10:10:22+00:00

Fixed: 1) Run "bitbake recipe" in the terminal 2) Close the terminal while building 3) $ ps aux | grep bitbake-worker There will be many processes, and they will keep the resources (e.g., memory), and won't exit unless kill or kill -9. (Bitbake rev: 72536d4e0cc3379001b730950afa012f7a96a79b) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bin/bitbake: Update to version 1.24.0

2014-09-23T21:10:12+00:00

(Bitbake rev: 637ce8df2658e4905fab8a0600a45505596bf472) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Fix bitbake -n

2014-09-22T14:54:40+00:00

Without this you see: File "bitbake/bin/bitbake-worker", line 201, in fork_off_task os._exit(child()) TypeError: an integer is required (Bitbake rev: cd477b5e77ab0373248b8a8fa30e1c7b8ea984fd) Signed-off-by: Richard Purdie

bitbake: bin/bitbake: Update to version 1.23.2

2014-09-11T16:31:17+00:00

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

bitbake: siggen/runqueue/bitbake-worker: Improve siggen data transfer interface

2014-09-11T16:31:17+00:00

We need to transfer some of the siggen data from the core/cooker into the worker instances. There was a partial API created for this but its ugly and its not possible to extend it from the siggen class. This patch completes the interface/abstraction for the data and means the class can extend/customise it in any siggen class. (Bitbake rev: cf2d642052979d236185c5b8ca2c5478c06e62ae) Signed-off-by: Richard Purdie

bitbake: toaster: bitbake server listen on all interface

2014-09-05T09:14:24+00:00

We change the toaster starting script to make the bitbake server listen on all interfaces on the local machine. This is needed to be able to receive a controlling client running on a remote machine. (Bitbake rev: 137179eafca8d1a5a69b6302f8cc8961be3b45c4) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: toaster: update checksettings command for auto-detection

2014-08-29T12:56:50+00:00

We enhance the checksettings command to try to automatically detect settings for running on localhost. The checksettings will look for a nearby poky layer source, for a nearby build directory, and will try to import settings from "toasterconf.json" files found in the local layer. On new configuration, it will also perform updates from the layer source. (Bitbake rev: 2aab77dfccb538e2b09829841ea6c464d40cafb1) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Extra profiling data dump

2014-08-28T14:12:45+00:00

Currently we get no profiling oversight into either the main bitbake worker process, or the overall parsing before task execution. This adds in extra profiling hooks so we can truly capture all parts of bitbake's execution into the profile data. To do this we modify the 'magic' value passed to bitbake-worker to trigger the profiling, before the configuration data is sent over to the worker. (Bitbake rev: 446e490bf485b712e5cee733dab5805254cdcad0) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Improve sigterm handler

2014-08-23T08:31:42+00:00

When processes terminate, we really want all of the child processes to terminate too. This was not happening for worker processes which spawned their own multiprocessing pools, leading to build hangs. This change ensures any sigterm gets passed to the whole process group. In local tests, this resolved some hanging process workloads I could generate. It does rely on signals being delivered in a timely fashion and there is a multiprocessing bug we have to work around there. (Bitbake rev: 96f8ea07ace1379380fab2d78eb592fa40c867d4) Signed-off-by: Richard Purdie

bitbake: bitbake: remove choices for dump-signatures

2014-07-24T11:31:39+00:00

The SIGNATURE_HANDLER can be defined by the user, so we can't use choices. (Bitbake rev: 0036b36e333a68c6d30a6bf5c21bfd4fd3e8441b) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie