summaryrefslogtreecommitdiff
path: root/bitbake/bin
AgeCommit message (Collapse)AuthorFiles
2011-01-04Don't show uncaught exception message for KeyboardInterruptChris Larson1
(Bitbake rev: 29634acd262b06fd14f6ef1e134346f274cf448f) 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 Larson1
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 logging in the knotty ui, and pass the log record across directlyChris Larson1
This kills firing of Msg* events in favor of just passing along LogRecord objects. These objects hold more than just level and message, but can also have exception information, so the UI can decide what to do with that. As an aside, when using the 'none' server, this results in the log messages in the server being displayed directly via the logging module and the UI's handler, rather than going through the server's event queue. As a result of doing it this way, we have to override the event handlers of the base logger when spawning a worker process, to ensure they log via events rather than directly. (Bitbake rev: c23c015cf8af1868faf293b19b80a5faf7e736a5) 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 Larson1
(Bitbake rev: 47ca82397bc395b598c6b68b24cdee9e0d8a76d8) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Ignore python warnings that come from places we don't care aboutChris Larson1
Only shows warnings that come from bb, oe, or <string> (Bitbake rev: 57018687f60b222ab220dd904c4bf870780171e9) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2011-01-04Drop the 'ui failed to start' message, as the ui_init does more in knottyChris Larson1
(Bitbake rev: 39087138ffd5d427f07ecaa580a40885c5ffaff3) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-12-10bitbake/bitbake-runtask: Since the parent has set the environment up cleanly ↵Richard Purdie1
we don't need to filter this ourselves anymore Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-12-09bitbake: Overhaul environment handlingRichard Purdie1
Currently, anything whitelisted in the environment makes it into the worker processes. This is undesireable and the worker environment should be as clean as possible. This patch adapts bitbake sosme variables are loaded into bitbake's datastore but not exported by default. Any variable can be exported by setting its export flag. Currently, this code only finalises the environment in he worker as doing so in the server means variables are unavailable in the worker. If we switch back to fork() calls instead of exec() this code will need revisting. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-11-14bitbake-runtask-strace: simple shell script to wrap tasks in a strace callJoshua Lock1
Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-11-13bitbake: Rewrite profiling code so its functional for both none and xmlrpc ↵Richard Purdie1
backends Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-10-14bitbake-runtask: Ensure logging settings take effect in the worker process ↵Richard Purdie1
(and pass verbose setting) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-10-11bitbake-runtask: Ensure logging options are inherited from the parentRichard Purdie1
[BUGID #291] Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-30bitbake/bitbake-sigdiff: Extend to handle dumping single state siginfo filesRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-29bitbake/bitbake-runtask: Signatures are needed in task context and have ↵Richard Purdie1
little overhead so enable in worker context Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-28bitbake: Pass task hash information to subprocessesRichard Purdie1
Pass task has informaiton to work processes, allowing full manipulation of the hash data in the task context allowing checksums to be usable. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-13bitbake/build.py: Set BB_FILENAME to represent the .bb file being built ↵Richard Purdie1
(including any virtual prefix) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-08bitbake: save the initial PATH for use when starting a subprocessJoshua Lock1
It was possible for bitbake-runtime to be run against a semi-installed python-native resulting in tracebacks with ImportError's. To prevent this we stash the initial PATH in the BBConfiguration when bitbake is started and then set this in the env when launching bitbake-runtask through subprocesses Popen() call. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2010-09-07bitbake/bitbake-runtask: Ensure signals to the parent don't pass to the ↵Richard Purdie1
children directly Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-03bitbake: Add missing signature filesRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-03bitbake: Implement signaturesRichard Purdie1
Includes functionality to find out what changes between two different singature data dumps. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-20bitbake: Correctly route events from the worker to the serverRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-19bitbake: Switch to use subprocess for forking tasks and FAKEROOTENV to run ↵Richard Purdie1
shell and python under a fakeroot environment Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-16*: use print() as a functionBernhard Reutner-Fischer1
to make python3 happy (Bitbake rev: c82926ccdd4ec4e3ad6e78a381dacb96adf9b409) Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Apply some 2to3 refactoringsChris Larson2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Until the interactive mode is fixed, kill it from the valid options, to ↵Chris Larson1
avoid confusion (Bitbake rev: 65a51bb20677148a29b9e472f6d9d0a97798f024) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Move serverConnection.terminate() back into the finallyChris Larson1
(Bitbake rev: 58e1b0a5dbd0f1ca137ad7ed1bd7ad9975a20fb7) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Limit the traceback length in the default exception handlerChris Larson1
(Bitbake rev: 2b9dc5b55e24b4946ff03bf30ca52a48547caaad) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Resurrect the excepthook, this time just sending the info with bb.fatalChris Larson1
(Bitbake rev: 07757a1bf1129cc6a967a7cf1815d3d46a6bbdcf) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02remove return in finally statementCliff Brake1
causes exceptions to not be handled after the finally statement (Bitbake rev: 1a04610dea376340b9ea4c109f64995b4fd6ad02) Signed-off-by: Cliff Brake <cbrake@bec-systems.com> Signed-off-by: Chris Larson <clarson@kergoth.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Drop the non-debug traceback suppressor, at this point I think it does more ↵Chris Larson1
harm than good (Bitbake rev: 2c66ddc2713061ba31363ea69c24944f4a7cd3a8) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Reorganize the main exception handling so an attribute exception raised in ↵Chris Larson1
the ui isn't misinterpreted (Bitbake rev: 49b8bab706c59e93287f8540187b62ba3ece0a11) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Adjust the exception handling based on Cliff Brake's patchChris Larson1
Rather than printing the exception ourselves, might as well re-raise and let the default exception handler do it for us. (Bitbake rev: acca7eb8450cbe30d65b5b266f1a642e7965df8a) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Fix the debug level check in print_exceptionChris Larson1
(Bitbake rev: 9cb52edf9198fe6db735abbb61d0c4026c97a8d9) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Move the python version check into the python packageChris Larson1
This ensures the check is run for anyone using the package, including setup.py, though it's sad that it's necessary, since all it really wants is __version__. Ideally, we'd avoid the version check entirely in favor of checking for functionality, but that's rather difficult with language constructs like context managers, so this'll do for now. (Bitbake rev: f936f1c0edf70860ea0f39ec1a500ba43b56f289) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Drop an unnecessary second python version check and use the less ugly ↵Chris Larson1
sys.version_info (Bitbake rev: 8f4b7b10f8740a41c085beeca5105f15204b0979) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Bump version to 1.11.0Chris Larson1
(Bitbake rev: 6c89c332664a7789d02a701e7e530838ab778264) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Move the python version check before the module imports, in case the modules ↵Chris Larson1
utilize the newer python features (Bitbake rev: 87c15dfcbeb10e7cafb14726209e4954671b3dbe) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Ignore deprecation warnings for nowChris Larson1
(Bitbake rev: 661fe59445161c5bc6a2e73b7fcbf9d20c492e27) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Import fixupsChris Larson1
(Bitbake rev: 4fa052f426e3205ebace713eaa22deddc0420e8a) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Formatting cleanupsChris Larson1
(Bitbake rev: 2caf134b43a44dad30af4fbe33033b3c58deee57) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Bump minimum python version check to 2.6.Chris Larson1
(Bitbake rev: 85c000cc7db47cfd489cf282c58db2dab0d87908) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Display python warnings via bb.msgChris Larson1
(Bitbake rev: 648415a562d92109c4945cb3cc98ed2ec44667a7) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Use __import__ for the ui rather than execChris Larson1
(Bitbake rev: 7d00bab300961431f9960cf6759966f608580bc0) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-07-02Initialize pkgs_to_build in the BBConfiguration constructorChris Larson1
(Bitbake rev: 69a3e4895b88110fd3a25167aa16cf7c00463175) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-29bitbake: create cooker object after cleaning the environmentJeff Dike1
Previously, the cooker object was created before the environment was cleaned, saving everything that was in the environment and dumping into the run scripts. The patch ensures that the cooker gets a cleaned environment when it's created. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-06-29bitbake: Move the logger initialization from cooker to utilsJeff Dike1
In order to move the environment cleaning, which wants to log a message, before cooker creation, the logging facility initialization needs to happen earlier. So, it is now in init_logger in utils.py and called from bitbake before the creation of the data object. It also seems more correct to initialize a global facility like this from a more global context than the creation of an object, of which there could theoretically be many. Signed-off-by: Jeff Dike <jdike@linux.intel.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-22bitbake: Don't import xmlrpc server unless neededRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-22bin/bitbake: Add import serverRichard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-21bitbake: Fix UI failure exception handling with python 2.6Richard Purdie1
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-01-20bitbake: Switch to bitbake-dev version (bitbake master upstream)Richard Purdie2
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-20 22:37:47 +0000