linux/poky.git/bitbake, branch yocto-3.4.4

bitbake: knotty: reduce keep-alive timeout from 5000s (83 minutes) to 10 minutes

2022-04-30T06:33:59+00:00

The keep alive timeout is excessively long at 83 minutes (5000 seconds), reduce this to 10 minutes: this should be long enough that it rarely triggers in normal builds, but when it does it has useful information. (Bitbake rev: c2d8f9b2137bd4a98eb0f51519493131773e7517) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit dcf52157d3635925491783be656c6b76d1efe1a4) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: knotty: display active tasks when printing keepAlive() message

2022-04-30T06:33:59+00:00

In interactive bitbake sessions it is obvious what tasks are running when one of them hangs or otherwise takes a long time. However, in non-interactive sessions (such as automated builds) bitbake just prints a message saying that it is "still alive" with no clues as to what tasks are active still. By simply listing the active tasks when printing the keep alive message, we don't need to parse the bitbake log to identify which of the tasks is still active and has presumably hung. (Bitbake rev: cc4e7d7049f949b54b1ea7926844b3c76f361c64) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 30f6c3f175617beea8e8bb75dcf255611e3fc2fd) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: server/process: Disable gc around critical section

2022-04-16T22:03:51+00:00

The python gc can trigger whilst we're holding the event stream lock and when cleaning up objects, they can trigger warnings. This translates into a new event which would then need the lock and we can deadlock. Disable gc whilst we hold that lock to avoid this unfortunate and problematic situation. (Bitbake rev: 70ea322a4866f7ef20361a6b146f2be568261c6a) Signed-off-by: Richard Purdie (cherry picked from commit 96a6303949cefd469bcf5ed250ff512271354357) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

bitbake: toaster: fixtures replace gatesgarth

2022-04-05T19:39:02+00:00

Add hardknott Add honister (Bitbake rev: 2d4cc6c4e75d0176d09dd30fbf209b3ed271ffb5) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: toaster: Fix IMAGE_INSTALL issues with _append vs :append

2022-04-05T15:55:33+00:00

After the override syntax change, toaster isn't working correctly. This is because it uses IMAGE_INSTALL_append instead of IMAGE_INSTALL:append. This tweaks the code accordingly to fix this. I have a suspicion that exiting toaster databases may struggle with the change and there are some migration steps missing for the whole overrides syntax change step. (Bitbake rev: 9b42537b41f25db4f57596ff24cf214576767cf1) Signed-off-by: Richard Purdie

bitbake: server/xmlrpcserver: Add missing xmlrpcclient import

2022-04-05T15:54:38+00:00

This avoids backtraces when starting toaster or using bitbake in remote mode. (Bitbake rev: 19c3ae42ea15e40f345bf16fe58b26fe451cb7fc) Signed-off-by: Richard Purdie

bitbake: build: Tweak exception handling for setscene tasks

2022-03-24T11:05:16+00:00

If an unexpected exception occurs in a setscene task, it is currently hidden from the user and not recorded in any logs. This isn't helpful to debug such failures. Change the code so that even in the "silent" or "quiet" task case (setscene tasks), a warning is shown with the traceback unless it was an "handled" exception. This means the failing function can show it's own warning/error instead if it wants to and then raise a handled event. (Bitbake rev: 43dcb2b2a2b95a5c959be57bca94fb7190ea6257) Signed-off-by: Richard Purdie (cherry picked from commit 41dcdc61eb40def8c14a42e8d7bb9ce5a34afa57) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: fetch2: ssh: username and password are optional

2022-03-14T13:33:35+00:00

Support URLs like ssh://HOST/PATH. They were previously not recognized due to a missing @ sign. (Bitbake rev: 1bc9f800ffc9b740cc1de0132ed04f07eadb3479) Signed-off-by: Daniel Wagenknecht Signed-off-by: Richard Purdie (cherry picked from commit a2aa18bd27dac8902e52b466cb7118f71367d3dc) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: utils: Ensure shell function failure in python logging is correct

2022-03-14T13:33:35+00:00

If a python function exec_func() calls a shell task, the logging wasn't working correctly in all cases since the exception was turned into a BBHandledException() and the logfile piece was lost which is handled at the top task level. The easiest way to avoid this is to allow the ExecutionError exceptions to be raised to a higher level, we don't need the traceback for them. (Bitbake rev: 23a6f11b089b14382c21d431edf34fa7224c66bf) Signed-off-by: Richard Purdie (cherry picked from commit 7cae11f558f9ff5fd05ef23b789aaef92fb5a327) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake: cooker: Improve parsing failure from handled exception usability

2022-03-14T13:33:35+00:00

When a recipe raises a BBHandledException, it means the error was already shown to the user. Adding an additional one here isn't helpful. What is helpful is to mention that parsing was halted. Tweak the code to do this with improves the messages the user sees and helps understand what happened. (Bitbake rev: b562966435ccd2335cfdccf89a9d7d18dd76a749) Signed-off-by: Richard Purdie (cherry picked from commit fdf6ebc8b603fcfd3ed7c64baf486a4adabd25be) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie