linux/poky.git/bitbake/bin, branch 1.6_M4

bitbake: bitbake-worker: Ensure children have default sigterm handler

2014-03-12T03:18:53+00:00

The children of the worker should have the default SIGTERM handler, else they'll try and do cleanup which should only happen in the parent leading to all kinds of bizarre build failures. (Bitbake rev: a53c8d1f846d94082aa459996c4114f10970b8ef) Signed-off-by: Richard Purdie

bitbake: bitbake: fix typo in variable name

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

When passing -t with an incorrect server type, the error message was using a variable that doesn't exist. (Bitbake rev: 98b991287df06cd89955c1d0591fce3b5d4403d1) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake: toaster: erase checks for stop command

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

We remove the checks for the stop command, since we assume the user really means it wants to shutdown the system when he issues the command. [YOCTO #5376] (Bitbake rev: 5d6594de8876be8ce4df56b846fee0fc687a6261) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Gracefully handle SIGTERM

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

Currently if bitbake-worker handles a SIGTERM, it leaves the child processes to complete or hang. It shouldn't do this so hook the SIGTERM event and gracefully shutdown any children. (Bitbake rev: 551406f3f9ee94de09d2da6e16fea054c6dbfdb7) Signed-off-by: Richard Purdie

bitbake: bitbake-selftest: enable specifying tests to run on command line

2014-02-28T14:50:43+00:00

If you are just trying to fix one test at a time, it can be useful to be able to specify an individual test(s) rather than running them all: bitbake-selftest bb.tests.codeparser bb.tests.cow You can even specify the test class or function to run, e.g.: bitbake-selftest bb.tests.fetch.URITest bitbake-selftest bb.tests.fetch.FetcherNetworkTest.test_fetch (Bitbake rev: 4df9c72663e972437131a848e6ddcf3769ae1d2b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: toaster: add two-stage commit startup logic

2014-01-07T13:03:05+00:00

Toaster start script lunches multiple process components of the toaster system. This patch adds logic into the startup script to safely fail startup and do proper cleanup on any error that may happen during system start. Bitbake needs to return 0 if it will successfully lunches the server-mode. (Bitbake rev: f43d284e7ae752049711d8215a6020bee6966d45) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: Update to version 1.21.1 for master

2013-12-20T12:26:06+00:00

(Bitbake rev: 4cc6e61fe11eb233bdba7c1bdc110b8cdafa56f8) Signed-off-by: Richard Purdie

bitbake: toaster: migrate orm models to South

2013-12-10T11:16:14+00:00

As Toaster advances, database schema alteration will force users to delete old versions and lose all data collected. In order to prevent this, and to allow database updates to happen without having to delete old data, we use South to handle migrations for the ORM application which stores the Toaster data. [YOCTO #5559] (Bitbake rev: 6936faed8d94f3a2ab4055049cd27d02d8229003) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: toaster: update to Django 1.5

2013-12-10T11:16:13+00:00

In order to remain up to date with the relevant technologies, Toaster is updated with this patch to Django 1.5. This also makes headways to allow usage of emerging Django-related technologies. Changes include the startup script Django version check, usage of TemplateView instead of deprecated simple function to do redirects, and update to the new form of the _url_ template tag. Support for Django 1.4.5 is now deprecated. [YOCTO #5558] (Bitbake rev: 2d37a1731a2b681bc976f3f391d65abb7745b6f9) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: bitbake.lock: Add host:port to bitbake.lock for memres server

2013-12-02T17:33:14+00:00

The idea is to build on the --status-only option for bitbake and expose a mechanism where the oe init scripts can easily switch between memres server and the non-memres server. In the case of the standard oe init script the following can shut down the server: if [ -z "$BBSERVER" ] && [ -f bitbake.lock ] ; then grep ":" bitbake.lock > /dev/null && BBSERVER=`cat bitbake.lock` bitbake --status-only if [ $? = 0 ] ; then echo "Shutting down bitbake memory resident server with bitbake -m" BBSERVER=`cat bitbake.lock` bitbake -m fi fi A similar function can be used to automatically detect if the server is already running for the oe memres init script. This new functionality allows for the memres init script to be started in a new shell and connect up to an alaready running server without seeing the error of trying to start the server multiple times. (Bitbake rev: b1803958de8d7c3c3279841e38604a08dc2316cc) Signed-off-by: Jason Wessel Signed-off-by: Richard Purdie