linux/poky.git/bitbake/bin, branch 5.2_M1

bitbake: bitbake-config-build: add an alias to bitbake-layers

2024-12-13T11:11:18+00:00

This alias is intended for managing specific local configs and it is prompted by adding support for config fragments (in a separate commit to oe-core); after some deliberation I concluded there should be a separate tool, as bitbake-layers is already somewhat over-stuffed, and this will give space for more build/conf/* operations in the future that anyone can come up with (such as tweaking site-specific items in site.conf etc.) The alias completely reuses existing code via symlink and the difference is in where it looks for plugins. (Bitbake rev: ba90fe673aa87cb0cda9b2e465ebe2063551f527) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: bitbake-layers: use 'with' to manage tinfoil context

2024-11-28T00:06:24+00:00

(Bitbake rev: bd468a5b9210043d0121a322360d976fd830f736) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie

bitbake: bitbake-getvar: Catch NoProvider exception

2024-11-21T12:16:28+00:00

When the recipe provided by (-r, --recipe) is not found tinfoil raises an exception that is not catched for readability, example: Traceback (most recent call last): File "/.../poky/bitbake/bin/bitbake-getvar", line 45, in d = tinfoil.parse_recipe(args.recipe) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/.../poky/bitbake/lib/bb/tinfoil.py", line 633, in parse_recipe fn = self.get_recipe_file(pn) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/.../poky/bitbake/lib/bb/tinfoil.py", line 550, in get_recipe_file raise bb.providers.NoProvider('Unable to find any recipe file matching "%s"' % pn) bb.providers.NoProvider: Unable to find any recipe file matching "aaa" (Bitbake rev: 06aa6c292813a28c84736193b550fb2d18884d43) Signed-off-by: Talel BELHAJSALEM Signed-off-by: Richard Purdie

bitbake: bitbake-worker/cooker: Increase default pipe size

2024-11-21T12:16:28+00:00

The default pipe size is 64kb on builds, which can be inefficient for larger log files from workers. Increase the pipe size to 512kb since build systems have decent amounts of memory and this is a more efficient way of batching the data. Tweak the default read sizes to match the pipe size for efficiency. Since the contstant is only present in python 3.10 onwards, add some compatibility code. (Bitbake rev: 69c14e46600ba5ae9703f67704ab2548875ae6d7) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Improve bytearray truncation performance

2024-11-21T12:16:28+00:00

If there are large amounts of data being transferred to the cooker from the worker, recreating the bytearray becomes inefficient as it happens for every pipesize block of data, defaulting to 64kb. Instead we can use the deletion API for bytearrays to make this more efficient and avoid the object recreation. We noticed this with a strace ptest image taking days to complete the build after having 6GB of data in the testimage log. Whilst there are other issues there, making this code more efficient doesn't hurt. (Bitbake rev: a4a72b7edb368f352784c856a647236a887010dd) Signed-off-by: Richard Purdie

bitbake: bitbake-layers: ensure tinfoil.shutdown() gets executed when tinfoil.prepare() fails

2024-11-21T12:16:28+00:00

https://git.yoctoproject.org/poky/commit/bitbake/bin/bitbake-layers?id=f6de2b033d32c0f92f19f5a4a8c4c8874a00a8f7 erroneously moved tinfoil.prepare() out of try..finally block, where 'finally' contains a tinfoil.shutdown() call. Without the shutdown, if there is an error in tinfoil.prepare() (such as parsing errors), the tool locks up, as seen here: https://valkyrie.yoctoproject.org/#/builders/71/builds/431 (Bitbake rev: 06b8a18339434be8f754e534dacb790a2c9cb91d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: bitbake-getvar: use finalizeData tinfoil API to get identical result to "bitbake -e"

2024-11-18T13:41:38+00:00

Fixes [YOCTO #15638] (Bitbake rev: 68ae81dc93f86eab378fec2276561c5062263d7e) Signed-off-by: Yoann Congal Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

bitbake: bitbake-hashclient: Add help for address

2024-10-25T14:40:03+00:00

Adds an epilog to the help text that indicates the possible options for the server address (Bitbake rev: b6b703fce02057212ad11b1d1286c6178c533bad) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

bitbake: bitbake-prserver: use PRSERV_UPSTREAM as default setting

2024-10-11T11:17:36+00:00

Instead of PRSERVER_UPSTREAM. The intended variable name is PRSERV_UPSTREAM, as already used in lib/prserv/serv.py, an consistently with the PRSERV_HOST variable name. (Bitbake rev: b0c277f16f9fae51914024c1daecd5d3e4fac5c2) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie

bitbake: bitbake-server: use with to avoid ResourceWarning

2024-10-11T11:17:36+00:00

Prevents the following warning in bitbake-cookerdaemon.log: 2386729 10:54:16.195427 Exiting (socket: True) 2386729 10:54:16.201065 Exiting as we could obtain the lock sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='/home/laplante/main_yocto/build/bitbake-cookerdaemon.log' mode='a+' encoding='UTF-8'> (Bitbake rev: 8dbf1ec8139d9dd7f52c1773cccbe7696b3ec1b4) Signed-off-by: Chris Laplante Signed-off-by: Richard Purdie