summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/__init__.py
AgeCommit message (Collapse)Author
2015-10-01bitbake: bitbake/lib: Update version to 1.28.0Richard Purdie
(Bitbake rev: 3e63abc6977bd5ef52ccb4d3757536bd564dfd34) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-16bitbake: lib/bb: provide mechanism to bypass UI log suppressionPaul Eggleton
The recent change to connect through the shell logging functions had an unexpected side-effect - bb.error() and bb.fatal() cause a flag to be set internally such that BitBake's UI will not print the full task log on failure; unfortunately we have in places within the OpenEmbedded metadata called these shell logging functions under error situations where we still want to see the full log (i.e., the message we're sending doesn't include the full error). Thus, provide a mechanism to fatally exit with an error but unset the flag, utilising the built-in python logging functionality that allows extra values to be passed in the log record. (Bitbake rev: e561b997c55e8537d82aa1339adfff4505cc38b7) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-06-09bitbake: bitbake: Bump version to 1.27.1Richard Purdie
(Bitbake rev: 430f7a288b4446600b3a943c51f6711ffcf9e619) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-25bitbake: Update to version 1.27.0 post 1.26 releaseRichard Purdie
(Bitbake rev: 0153e0b4e089f62a7d5a92ca6be2fa5a8f61a6e4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-25bitbake: Update to version 1.26.0Richard Purdie
(Bitbake rev: 14da7bc06bc6ea6fd051c0afd8d4839d96f415e7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-03bitbake: bitbake: Update to 1.25.0 as development version after releaseRichard Purdie
(Bitbake rev: 94d9590a4310f96396e8e782bcf65918f4dcdb36) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-23bitbake: bin/bitbake: Update to version 1.24.0Richard Purdie
(Bitbake rev: 637ce8df2658e4905fab8a0600a45505596bf472) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-09-11bitbake: bin/bitbake: Update to version 1.23.2Richard Purdie
(Bitbake rev: e24095f54c52a547c0462836586a5d716249036e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-08-25bitbake: lib/bb/*.py: Typo fixes/grammar/comment fixes, nothing functional.Robert P. J. Day
(Bitbake rev: 587b144ee409d444494d8d7f2d1c53ede8f7c953) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-06-01bitbake: bb.fatal: Raise a BBHandledException instead of exitingRichard Purdie
With new bitbake UIs having the cooker exit at 'random' points in the codebase is problematic. This patch raises an exception which matches the situation instead. (Bitbake rev: 181a9735d02ebd517378558e909efc8b1b118973) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-05-01bitbake: bitbake: Bump version to 1.23.1Richard Purdie
(Bitbake rev: c40a4100ddb841d231360344616e59ab98e61fb5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-10bitbake: bitbake: Update to version 1.23.0 for masterRichard Purdie
(Bitbake rev: bb4980c63db386ce7d30d9a6b86e9f3861b3bc3a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-10bitbake: bitbake: Update to version 1.22.0Richard Purdie
(Bitbake rev: a8a32de0fb74ff63e5490e3b5e4419146a8f7367) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-20bitbake: Update to version 1.21.1 for masterRichard Purdie
(Bitbake rev: 4cc6e61fe11eb233bdba7c1bdc110b8cdafa56f8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-14bitbake: bitbake: bitbake: bb: Drop deprecated functionsRichard Purdie
These functions in the main bb module have long been deprecated and moved to other modules. Finally remove the compatibility links. (Bitbake rev: ccd181c3ed4852e2b9169cf19aaf18aeacddcc18) (Bitbake rev: d7f817518c5df2524a4bcf008ba63c71a8eb48bb) (Bitbake rev: 89b31a4fb44f2c2ad0bb4210151652cd3730418d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-14bitbake: bitbake: Update post 1.20 to development versionRichard Purdie
(Bitbake rev: 03d051b6da52ec4ee26f97aa9038622f8d87e55d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-24bitbake: bitbake: Update to version 1.20.0Richard Purdie
(Bitbake rev: 2666865a27cedbffc82800b4cab1d6cff5a0222e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-17bitbake: Revert "bb.fatal: Raise a BBHandledException instead of exiting"Richard Purdie
Sanity test failures are no longer fatal with this change so whilst its the right idea, the code paths need more work. This reverts commit a50017ba71250e1710a6425b60ac7e3f03d88295. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-17bitbake: bb.fatal: Raise a BBHandledException instead of exitingRichard Purdie
With new bitbake UIs having the cooker exit at 'random' points in the codebase is problematic. This patch raises an exception which matches the siutation instead. (Bitbake rev: a50017ba71250e1710a6425b60ac7e3f03d88295) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14bitbake: bitbake: Update version to 1.19.1Richard Purdie
(Bitbake rev: 6acd444a557bba977ae1772371fdadf5f510e3b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14bitbake: bitbake: Bump minimum python version to 2.7.3Richard Purdie
(Bitbake rev: a01d153a8baac7136c2797c95357e74dd8872026) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-03bitbake: Update to version 1.19.0 for masterRichard Purdie
(Bitbake rev: c47088a86fd8ad06c1810d04d9537c4cd01e8bef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-10bitbake: Update to version 1.18.0Richard Purdie
(Bitbake rev: 94b54788cadabf6ebfb7711674646dbea6204805) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-06bitbake: Update version to 1.17.0Richard Purdie
(Bitbake rev: d96ef9398356b2a61f7cff765821616bf1e55492) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-14bitbake: bin/bitbake, bb/__init__: Move BBDEBUG handling to bin/bitbakeRichard Purdie
The method this older code was accessing doesn't exist. A library shouldn't be changing behaviour based on the environment anyway when sepcific function calls exist to correctly setup the logging. Fix the crash if BBDEBUG was used by moving the code to bin/bitbake. [YOCTO #3319] (Bitbake rev: 3a1b75037fe1e5282ffd40b037e93353405faa45) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26bitbake: Update version to 1.17.0Richard Purdie
(Bitbake rev: cc7fdbdc607df530f5539b162831bf9998eb48d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02bitbake: Update version to 1.16.0Richard Purdie
(Bitbake rev: a579754a04bdcf450e6957dde614a15c11df39e2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-19bitbake: Update version to 1.15.3Richard Purdie
(Bitbake rev: befbb5c9428eaf98b2ff9c4b36b0b3f2dce7fe07) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-01Update version to 1.15.2 (correspdoning to Yocto 1.2 release)Richard Purdie
(Bitbake rev: 270a05b0b4ba0959fe0624d2a4885d7b70426da5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-05bitbake: Drop fetch v1, v2 provides a much better codebase to build fromRichard Purdie
(Bitbake rev: 292e3430e5140b602cad86f55b5453e8cebb28a1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-23Bump the version to 1.15.1Richard Purdie
(Bitbake rev: 65c2eb1c095fe7ba3259060aefd4ba0e20cae319) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-10bitbake: Add BBHandledException exception classRichard Purdie
We have a problem knowing when to show the user debug information and when not to since the code has already shown the user suitable information about why a failure is occurring. This patch adds a bb.BBHandledException exception class which can be used to identify those exceptions which don't need further explanation to the user. This patch uses this class for the bb.providers exceptions and ensures the command handling code correctly filters the exceptions meaning that "bitbake invalid" now shows an simple error message and not a python traceback. [YOCTO #1141 partial] (Bitbake rev: eac9249b40ae1e3aa21e016010c862664e59a8d4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-04Increment version post releaseRichard Purdie
(Bitbake rev: 9c097704b4309dbe67fc360c8377edbedc354d00) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-04Release 1.14.0Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-10-11Fix typos in local.conf.sample and local.conf.sample.extendedRobert Yang
Fixes bug [YOCTO #1667] Fix typos in local.conf.sample and local.conf.sample.extended: differernt -> different chages -> changes complation -> compilation egde -> edge "an an" -> "as an" images's -> image's Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-15bitbake/logging: Overhaul internal logging processRichard Purdie
At the moment it bugs me a lot that we only have one effective logging level for bitbake, despite the logging module having provision to do more advanced things. This patch: * Changes the core log level to the lowest level we have messages of (DEBUG-2) so messages always flow through the core logger * Allows build.py's task logging code to log all the output regardless of what output is on the console and sets this so log files now always contain debug level messages even if these don't appear on the console * Moves the verbose/debug/debug-domains code to be a UI side setting * Adds a filter to the UI to only print the user requested output. The result is more complete logfiles on disk but the usual output to the console. There are some behaviour changes intentionally made by this patch: a) the -v option now controls whether output is tee'd to the console. Ultimately, we likely want to output a message to the user about where the log file is and avoid placing output directly onto the console for every executing task. b) The functions get_debug_levels, the debug_levels variable, the set_debug_levels, the set_verbosity and set_debug_domains functions are removed from bb.msg. c) The "logging" init function changes format. d) All messages get fired to all handlers all the time leading to an increase in inter-process traffic. This could likely be hacked around short term with a function for a UI to only request events greater than level X. Longer term, having masks for event handlers would be better. e) logger.getEffectiveLevel() is no longer a reliable guide to what will/won't get logged so for now we look at the default log levels instead. [YOCTO #304] (Bitbake rev: 45aad2f9647df14bcfa5e755b57e1ddab377939a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-07-25Update version to 1.13.3Richard Purdie
(Bitbake rev: f0b5d16426b983a67c51c47f3542162108bd4156) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-28Update version to 1.13.2Richard Purdie
(Bitbake rev: 5d41720d1550c04aac76275614ca15110c1c7f52) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-09Update version to 1.13.1Richard Purdie
(Bitbake rev: c3c2ad6f22e35b893a353d4c21d0e923e46ad07b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-08Shift traceback pre-formatting into LogHandlerChris Larson
It's cleaner to leave it behaving as usual, passing the exception data in the exc_info attribute of the LogRecord where it normally lies, and then let LogHandler make it pickleable so it can be sent to the UI. (Bitbake rev: 3539c9474a0b53f57e614544c70a7197ecdfb130) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-06-08bitbake/lib/bb/__init__.py: Sync with upstream bitbakeRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-02-07bitbake:__init__.py: Fix debug log level handling to correct debug outputRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-10Inject taskpid into log records via our log handlerChris Larson
It turns out that while log filters added with addFilter are only associated with that logger, and not its children, handlers are inherited, and handlers can be filters. So, let's add filtering to our existing LogHandler class which dispatches our log records as bitbake events. (Bitbake rev: 0153ace246e7c88366f45c8f035a2b4505a1c115) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-10bitbake: For poky only, force the use of fetch2 codebaseRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-10bitbake: Switch to fetch2 fetcher code based on the environment variable ↵Richard Purdie
BBFETCH2 Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-08bitbake/__init__.py: Add taskpid to all LogRecords (subclassed to be ↵Richard Purdie
BBLogRecords) This allows us to identify which task messages are from. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-04Work around issue with pickling of traceback objectsChris Larson
(Bitbake rev: 82928613256bad92fde9f4071244a53e20fc89ee) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Apply fix for issue where the loggers were constructed with the wrong classChris Larson
(Bitbake rev: 1b21daf052c49f3126dac001712ec01ad63c5f60) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Switch bitbake internals to use logging directly rather than bb.msgChris Larson
We use a custom Logger subclass for our loggers This logger provides: - 'debug' method which accepts a debug level - 'plain' method which bypasses log formatting - 'verbose' method which is more detail than info, but less than debug (Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Use the python logging module under the hood for bb.msgChris Larson
(Bitbake rev: 47ca82397bc395b598c6b68b24cdee9e0d8a76d8) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-03 23:00:16 +0000