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

bitbake: fetch2/git: Allow other namespaces than refs/heads to be searched.

2015-01-06T14:15:48+00:00

This makes it possble to fetch Gerrit review references which are normally stored under refs/changes. Please disregard previous patch with the same topic. (Bitbake rev: ab8cbf2a71750f5ea36e218036b050857301607b) Signed-off-by: Fredrik Svensson Signed-off-by: Richard Purdie

bitbake: progressbar: use '/usr/bin/env' in shebangs with python

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

To support yocto on systems with python3 as default version, scripts should use /usr/bin/env python in the shebang, as this allows the use of a fake env to mimic python2 as default version. This patch simply replaces occurrences of #!/usr/bin/python with #!/usr/bin/env python and was done with this oneliner: git grep -lE '^#!/usr/bin/python' | xargs \ sed -i 's|/usr/bin/python|/usr/bin/env python|' (Bitbake rev: 0f9823adb7832c4ca3b2985391473aa6e8c22148) Signed-off-by: Martin Hundebøll Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

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: event: fix resetting class handlers object

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

If you don't explicitly specify to use a global variable when doing an assignment, you will be setting a local variable instead, which means this function wasn't working at all. It explains some odd behaviour we have seen in the layer index where event handlers were sometimes bleeding into other contexts where they should not have been. (Bitbake rev: f12c738d3dc1f0fd105d457385511440024bffab) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: data: Handle BASH_FUNC shellshock implication

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

The shellshock patches changed the way bash functions are exported. Unfortunately different distros used slightly different formats, Fedora went with BASH_FUNC_XXX()=() { echo foo; } and Ubuntu went with BASH_FUNC_foo%%=() { echo foo; }. The former causes errors in dealing with out output from emit_env, the functions are not exported in either case any more. This patch handles things so the functions work as expected in either case. [YOCTO #6880] (Bitbake rev: 4d4baf20487271aa83bd9f1a778e4ea9af6f6681) Signed-off-by: Richard Purdie

bitbake: runqueue: Fix 100% cpu use after keyboard interrupt

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

After Ctrl+C is pressed to interrupt bitbake, it loops continually, running at 100% cpu. This patch selects on the correct file descriptors resolving the excess cpu usage. (Bitbake rev: dca5d82830ef2838439e5272da9dac1f28954cf1) Signed-off-by: Richard Purdie

bitbake: buildinfohelper: Make sure we use the orm defined value for loglevel

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

We need to consistently use LogMessage.INFO/WARNING/ERROR to make sure toaster knows how to categories these rather than passing in the "raw" loglevel value which in best case comes from python logging but worst case any value. [YOCTO 6885] (Bitbake rev: 926235aad806232bc73e33d6dd8955dd26562e6b) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: prserv: Use WAL mode

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

Ideally, we want the PR service to have minimal influence from queued disk IO. sqlite tends to be paranoid about data loss and locks/fsync calls. There is a "WAL mode" which changes the journalling mechanism and would appear much better suited to our use case. This patch therefore switches the database to use WAL mode. With this change, write overhead appears significantly reduced. (Bitbake rev: 90b05e79764b684b20ce8454e89f05763b02ac97) Signed-off-by: Richard Purdie

bitbake: prserv/serv: Ensure sync happens in the correct thread

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

The sync/commit calls are happening in the submission thread which can race against the handler. The handler may start new transactions which then causes the submission thread to error with "cannot start a transaction within a transaction". The fix is to move the calls to the correct thread. (Bitbake rev: 08cf468ab751f4c6e4ffdab2d8e5d748f7698593) Signed-off-by: Richard Purdie

bitbake: prserv: don't wait until exit to sync

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

In the commit 'prserv: Ensure data is committed', the PR server moved to only committing transactions to the database when the PR server is stopped. This improves performance, but it means that if the machine running the PR server loses power unexpectedly or if the PR server process gets SIGKILL, the uncommitted package revision data is lost. To fix this issue, sync the database periodically, once per 30 seconds by default, if it has been marked as dirty. To be safe, continue to sync the database at exit regardless of its status. (Bitbake rev: 973ac2cc63323ca9c3e916effa4765747db3564c) Signed-off-by: Ben Shelton Signed-off-by: Richard Purdie