linux/poky.git/bitbake/lib/bb, branch 1.6_M4

bitbake: toaster: write files-in-image to the database

2014-03-11T19:24:30+00:00

Adding code to write files-in-image data from the metadata event to the database. (Bitbake rev: f3a69ef7cc536a4b879d60936199a1002584c4f4) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: runqueue: Use SIGCHLD instead of polling waitpid

2014-03-10T18:10:02+00:00

Instead of a significant number of calls to waitpid, register a SIGCHLD handler instead. (Bitbake rev: 76029d08ad56a0a264ff9738a0336971a455b7f5) Signed-off-by: Richard Purdie

bitbake: server/process: Optimise latency when finishing idle functions

2014-03-10T18:10:02+00:00

When idle functions finish, its likely we have some other work to do, so don't sleep in the select call but instead, skip it. This removes small amounts of latency in common commands. (Bitbake rev: 069d6538f83b607cb46c6fe21bf6c596e8b99242) Signed-off-by: Richard Purdie

bitbake: server/process: Drop unnecessary exit delay

2014-03-10T18:10:01+00:00

When the server exits, we no longer appear to need this delay. This is likely due to improvements in the various exit codepaths. There is therefore no longer any point in taking the latency hit. (Bitbake rev: 8e75ee29ae07e13f23525c5c6045fbf6cdbe7675) Signed-off-by: Richard Purdie

bitbake: server/process: Use a pipe for quit events instead of Event()

2014-03-10T18:10:01+00:00

Its not possible to notice the change of status of an Event() in the select call we sleep in. It would be possible in python 3.3 but for now use a pipe instead. This removes small latency when bitbake commands finish since the system doesn't sit in the select call. (Debugging these kind of issues is apparent by setting a long sleep for the select call) (Bitbake rev: def28239b0f0d5f1cf13214b263114a5328538b7) Signed-off-by: Richard Purdie

bitbake: knotty: Remove latency when exiting

2014-03-10T18:10:01+00:00

There is no point in waiting 0.25s for when we should be processing the shutdown. This simply reordering removes latency from the bitbake command. (Bitbake rev: f147b41bcaf9d05b5ba3a70100f1ca799979aee7) Signed-off-by: Richard Purdie

bitbake: knotty: Add missing continue statement for runQueueExitWait event

2014-03-10T18:10:00+00:00

The continue statement was missing for this event and the event was then listed in the "known safe to ignore list". Clean this up. (Bitbake rev: c4ee342300bf905e6e3bef581c61b86289461536) Signed-off-by: Richard Purdie

bitbake: providers/runqueue/taskdata: Optimise logger.debug calls

2014-03-10T18:10:00+00:00

A run of "bitbake bash -c unpack" when the task has already been completed resulted in about 9000 calls to logger.debug(). With this patch which comments out some noisy/less usefull logging and moves other logging calls outside loops, this number is reduced to 1000 calls. This results in cleaner logs and gives a small but measurable 0.15s speedup. The log size dropped from 900kb to 160kb. (Bitbake rev: d2677f084fe1d8846db77d89ef5e6ffb18dc171a) Signed-off-by: Richard Purdie

bitbake: cooker: Handle SIGTERM more gracefully

2014-03-10T18:10:00+00:00

If the cooker receives a SIGTERM it currently hangs using 100% CPU, This patch adds in an intercept for the event and puts the cooker into shutdown mode allowing it to exit cleanly/safely and avoiding the hang. (Bitbake rev: 00c22434123739b0819b31d7b1d353901a3e12da) Signed-off-by: Richard Purdie

bitbake: server/process: Deal more gracefully with SIGTERM

2014-03-10T18:09:59+00:00

Currently a SIGTERM to the UI process causes the UI simply to lock up. By setting an exit flag, the waitEvent can raise a SIGINT, allowing the UI to break out the event loop and exit. Currently this is results in a traceback but that is more desirable than a hanging process. (Bitbake rev: 0d12041eceeae6bba2034b04913bb13abd67bd15) Signed-off-by: Richard Purdie