linux/poky.git/bitbake/lib/bb/init.py, branch yocto-3.1.7

bitbake: init.py: Fix bitbake debug log handling

2021-03-09T00:03:55+00:00

For a while I've been puzzled as to why debug logging from runqueue wouldn't appear on the console with -DD. The logic in the bbdebug handling is inverted so fix it and now we see the expected messages from runqueue with -D and -DD. This should then let us debug other issues using those log messages. (Bitbake rev: e0dd20a006ce6fdc656e6be6ac581e93e2ed4a95) Signed-off-by: Richard Purdie

bitbake: bitbake: Update to version 1.46

2020-04-06T15:43:38+00:00

(Bitbake rev: 76396230731432b38fdcb25ad27bb84065bc89e5) Signed-off-by: Richard Purdie

bitbake: lib/bb/msg: Use log level instead of debug count

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

Passes around the actual logging level as the default log level variable instead of the debug count. This makes it easier to deal with logging levels since the conversion from debug count and verbose flag only has to occur once when logging is initialized and after that actual log levels can be used (Bitbake rev: 41bd155faf7f65cb0727fcce972715769b26ca89) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: lib/bb/msg: Convert default domains to a dictionary

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

Converts the default domain variable to a dictionary where the keys are the logging domains and the values are the logging level (instead of the debug count). This makes it easier to deal with the logging domains and the awkward conversion from a list to a dictionary only needs to be done once when logging is initialized. Finally, other code has been written that already assumes this variable is a dictionary, see: f04cd93109 ("bitbake: lib/bb: Optimise out debug messages from cooker") (Bitbake rev: f32a8bc7ff7a0b0750b6934a96f5d48391b1383a) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: lib/bb: Optimise out debug messages from cooker

2019-12-16T23:27:14+00:00

We have bb.debug(2, xxx) messages in cooker which are useful for debugging but have really bad effects on performance, 640,000 calls on recent profile graphs taking tens of seconds. Rather than commenting out debug which can be useful for debugging, don't create events for debug log messages from cooker which would never be seen. We already stop the messages hitting the IPC but this avoids the overhead of creating the log messages too, which has been shown to be signficiant on the profiles. This allows the code to perform whilst allowing debug messages to be availble when wanted/enabled. (Bitbake rev: f04cd931091fb0508badf3e002d70a6952700495) Signed-off-by: Richard Purdie

bitbake: Bump minimum python version to 3.5

2019-12-16T23:27:14+00:00

The local hash equivalence server used by bitbake requires python 3.5, so bump up the minimum required version. [YOCTO #13678] (Bitbake rev: 1412dcc077b1bea10b72fc8b525d6258dca46d97) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: bitbake: Update to version 1.44.0

2019-10-09T13:10:48+00:00

(Bitbake rev: 5d83d828cacb58ccb7c464e799c85fd2d2a50ccc) Signed-off-by: Richard Purdie

bitbake: bitbake: Bump verison 1.43.1 -> 1.43.2

2019-10-02T19:22:25+00:00

This allows metadata to depend on SignatureGeneratorUniHashMixIn which was recently added. (Bitbake rev: f0f814407fdd2fffa7071c36c011b489bfcd53da) Signed-off-by: Richard Purdie

bitbake: bitbake: Bump version to 1.43.1 for API changes

2019-08-06T10:21:32+00:00

(Bitbake rev: f43778c2d19e70d4befd483b06aaf247fc65c799) Signed-off-by: Richard Purdie

bitbake: bitbake: Strip old editor directives from file headers

2019-05-04T09:44:10+00:00

There are much better ways to handle this and most editors shouldn't need this in modern times, drop the noise from the files. Its not consitently applied anyway. (Bitbake rev: 5e43070e3087d09aea2f459b033d035c5ef747d0) Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb/__init__.py, branch yocto-3.1.7

bitbake: __init__.py: Fix bitbake debug log handling