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

bitbake: buildinfohelper: Drop unused variables

2022-04-21T20:00:35+00:00

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

bitbake: ui/knotty: Drop pointless pass statement

2022-04-21T20:00:35+00:00

(Bitbake rev: 625565087d8c9e7a6a79b0b4f3e5be2d77d5f100) Signed-off-by: Richard Purdie

bitbake: buildinfohelper: Drop unused function

2022-04-21T20:00:35+00:00

The function has a loop where the variable is never used which I was going to fix but the entire function never seems to be called so remove it entirely. (Bitbake rev: 3bcb20f025907f4e88bbe3d14f5638d5f01010cb) Signed-off-by: Richard Purdie

bitbake: ui/buildinfohelper: Drop unused import

2022-04-21T20:00:35+00:00

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

bitbake: knotty.py: Show elapsed time also for tasks with progress bars

2022-04-05T09:50:08+00:00

While the progress bar is good at conveying information about how much of a task has executed, the elapsed time of the task is still very much relevant to show. (Bitbake rev: 41eeb4f34fb2306303f7688ec5e0ae965a573aa4) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

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

2022-03-23T12:08:56+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: 2e47346b95b09d7ab8f0603e2d62cfb549dc1f5c) (Bitbake rev: dcf52157d3635925491783be656c6b76d1efe1a4) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

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

2022-03-23T12:08:56+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: f9f57fb7d2c8a13df1eb9d5b9766f15e229dcf97) (Bitbake rev: 30f6c3f175617beea8e8bb75dcf255611e3fc2fd) Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

bitbake: toaster: race condition for end-of-build

2022-03-21T10:07:40+00:00

Force a sync point for end-of build event handler force the build's outcome status commit, to resolve a race condition with the build completion takedown. [YOCTO #14765] (Bitbake rev: f76c13536e19d2401365c0fc240ef8dbcb3ee7e8) Signed-off-by: David Reyna Signed-off-by: Richard Purdie

bitbake: bitbake: buildinfohelper.py fix for Django 3.2

2022-03-15T08:40:09+00:00

connection.features.autocommits_when_autocommit_is_off was deprecated in 3.0 and is no longer present in 3.2 (Bitbake rev: cc0f526fb4298349d0eea44c8f35d3dd226cc8d6) Signed-off-by: Tim Orling Signed-off-by: Richard Purdie

bitbake: knotty.py: A little clean up of TerminalFilter::updateFooter()

2022-03-11T06:56:01+00:00

* Use max() to clamp progress to >= 0. * Be consistent when evaluating self.quiet (treat it as a boolean). (Bitbake rev: 160f71372ff93894d9314619e9d3b547c1f3cda3) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie