linux/poky.git/bitbake/lib/bb/ui, branch yocto-3.1.11

bitbake: taskexp: update for GTK API changes

2020-12-01T22:05:12+00:00

The introspected API for GtkTreeModel and friends had some unexpected quirks which have now been fixed, see[1] for details. However, for example Ubuntu 20.04 has the fixed GTK but not an updated pygobject which means taskexp raises an exception on startup. Solve by manually looking at what functions are present and calling the right one. [ YOCTO #14055 ] [1] https://gitlab.gnome.org/GNOME/pygobject/-/commit/9cdbc56fbac4db2de78dc080934b8f0a7efc892a (Bitbake rev: d171188cf966852326916f726cbd3ca9627b831c) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit ac7d1114a7e99e6efd6a37b03d170faf678513fb) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: ui/teamcity: don't use removed logging classes

2020-07-19T15:22:12+00:00

Allows the TeamCity frontend to be used again. (Bitbake rev: cea130b238e874bae30e13b3242a00eaff7f853b) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie (cherry picked from commit c5477ba79fcad4a887808dd0df9cfe3554e2c17a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: lib/ui/taskexp: Fix missing Gtk import

2020-07-19T15:22:12+00:00

Adding back gtk objects import. Fix bug introduce when adding validation on gtk import. (Bitbake rev: 44e24fffc568dfee054b5feff2d9b382b9ce4bb5) Signed-off-by: David Khouya Signed-off-by: Richard Purdie (cherry picked from commit 765be5ef60668f8a1cfbcba248f4995725807196) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: lib/ui/taskexp: Validate gi import

2020-07-19T15:22:12+00:00

When running bitbake -g -u taskexp without having gi python module or and invalid gtk version, bitbake fails with a stack trace. In case of import or version error, bitbake should exit with an error message instead of a stack trace. (Bitbake rev: 45e32f2651d35bf7a315af95cfe0b1070e038c9e) Signed-off-by: David Khouya Signed-off-by: Richard Purdie (cherry picked from commit 2a2c507f239b047f34765312df4168030e38b90d) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: knotty/msg: Use logging.shutdown() instead of bb.msg.cleanupLogging()

2020-03-13T11:29:23+00:00

The logging module provides a shutdown() function that does the same thing in a much better way (Bitbake rev: 970cd2fc4f0bbc93069dee5a15a608dd76081c67) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: knotty: Treat verbconsole as a console output

2020-03-13T11:29:23+00:00

The BitBake.verbconsole needs to be treated like a console output logger (meaning that the TerminalFilter attaches an InteractConsoleLogFilter to it), even if it's not directly attached to the root 'BitBake' logger. First, assign a special "is_console" property to the relevant handlers, then look for the property in the handlers from the configuration object return by bb.msg.setLoggingConfig(). Finally, pass the list of all handlers to the TerminalFilter object; it doesn't care about the difference between console and errconsole, so pass all the relevant handlers as a list. This fixes cases where the console output was corrupted when messages were sent to the 'BitBake.verbconsole' handler. (Bitbake rev: 2010be588c74a99256df7b565a309c84c2973546) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: knotty: Update hash equivalence logging

2020-03-13T11:29:23+00:00

Updates hash equivalence logging so that the interesting VERBOSE messages are always logged to the consolelog file so that issues in individual user builds can be diagnosed. The autobuilder logging config then updates this so that they also are shown on stdout, since the consolelog file is not capture there. In order to facilitate this, 2 new logging handlers were added, "BitBake.verbconsole" and "BitBake.verbconsolelog". Neither of these handlers are attached to anything by default, but they will log any messages that wouldn't otherwise be logged by the normal console or consolelog handlers. Users can attach whatever loggers the desire to this handler to get them to appear on the console or in the consolelog, as demonstrated by the autobuilderlog.json file. (Bitbake rev: 766587c0baaaeb5cda3e9454395edbb70e33f756) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: knotty: Add logging cleanup

2020-03-13T11:29:23+00:00

Adds code to close all loggers when bitbake exits. This prevents unclosed file ResourceWarnings. A form of this closing existed previously, but was removed in the new logging code. (Bitbake rev: b3f3779adf63c0d970462a558a6205da1d30c0ed) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: knotty: Setup logs with config helper

2020-03-13T11:29:23+00:00

Sets up logging in knotty to use python's structured logging config and the bb.msg.setLoggingConfig() helper to setup logging. This allows the user to specify additional logging mechanism in a config file with BB_LOGCONFIG (Bitbake rev: 646a68a49364b50a42168b4b16308f7217eec0dc) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: knotty: Remove dependency on format variable

2020-03-13T11:29:23+00:00

Passing around the log formatter variable was unnecessary since the log levels of interest can be accesses as class members of bb.msg.BBLogFormatter. Switching to do this will make using the structured python logging much easier, since it can be difficult to extract out the formatter for a specific handler. (Bitbake rev: c1c867df24b4ef204027d485acac7c75c63f2bc0) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie