linux/poky.git/bitbake/bin, branch 3.5_M2

bitbake: bitbake-worker: Add/support network task flag

2022-01-12T21:10:24+00:00

This patch changes behaviour. After this change any task which does not have the network flag set will have networking disabled on systems that support that (kernel version dependent). Add a "network" task specific flag which then triggers networking to be enabled for this task, it is otherwise disabled. This needs to happen before we enter the fakeroot environment of the task due to the need for the real uid/gid which we save in the parent process. (Bitbake rev: 0746b6a2a32fec4c18bf1a52b1454ca4c04bf543) Signed-off-by: Richard Purdie

bitbake: lib/bb: Clean up use of len()

2021-11-03T10:12:42+00:00

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

bitbake: bitbake: Bump to post release verion 1.53.0

2021-10-26T13:03:45+00:00

(Bitbake rev: 17d74fc64003770a94dfffa2ab102254fa52d585) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Add debug when unpickle fails

2021-10-17T10:57:27+00:00

We occasionally see bitbake-worker failing and from the logs, an unpickle error occurs. Add more debug so we can further debug this next time it fails. [YOCTO #14595] (Bitbake rev: fe8105cc06beca8240b76ea366a1eff5aa9c5412) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Set BB_CURRENTTASK earlier

2021-10-14T21:37:43+00:00

For some debugging, BB_CURRENTTASK is set too late to be useful as it isn't present in some event handlers for example. There is no other way to know which task is actually running so set the value earlier. (Bitbake rev: 7daaaaa27f55b5a458656857c6d61a51b34a62fe) Signed-off-by: Richard Purdie

bitbake: bitbake: Bump to version 1.52.0

2021-10-11T10:06:18+00:00

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

bitbake: bitbake-worker: Handle pseudo shutdown in Ctrl+C case

2021-10-08T15:45:06+00:00

If the build is interrupted, handle the shutdown of pseudo even in this case to avoid data corruption inside docker containers. [YOCTO #14555] (Bitbake rev: a2a04c6fe94bc56efcff299c669a151746e35916) Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Allow shutdown/database flush of pseudo server at task exit

2021-09-26T13:37:34+00:00

We have a problem where pseudo server processes exist after bitbake exits and hold the pseudo database in memory. In a docker container, the processes will be killed as the container is destroyed with no warning and no opportunity to write the data to disk. This leads to permissions/inode corruptions and data loss. Send a shutdown message to pseudo which in new versions of pseudo will flush the database, thereby fixing some of the issues people using docker containers see. (Bitbake rev: a07a971b40acd3eee12e203d2cfa3e49f56109f6) Signed-off-by: Richard Purdie

bitbake: bitbake: enable python warnings at the first opportunity

2021-09-19T10:33:14+00:00

We really do want to see those, as they tend to turn into hard errors eventually, as what happened with collections vs collections.abc in python 3.10. (Bitbake rev: bc43fbb86361a21dc2d5deb910810c5a77fdabe8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

bitbake: bitbake-worker: Improve error handling

2021-09-16T08:51:14+00:00

If bitbake-worker fails, return an error code showing that. Also make the thread cleanup code explict in a finally clause as it would otherwise hang. [YOCTO #14393] (Bitbake rev: 7e0af70fb53fb13f824ca954b8cc1dffee730233) Signed-off-by: Richard Purdie