diff options
| author |   Ross Burton <ross@burtonini.com> | 2022-06-16 15:48:49 +0200 |
|---|---|---|
| committer |   Steve Sakoman <steve@sakoman.com> | 2022-06-16 07:15:39 -1000 |
| commit | 36fe8bae9fec61547ee0b13bcb721033afd3ac0e (patch) | |
| tree | 7927be2de82dead21f3975363e5c6f48af7bab74 | |
| parent | 47ed06d441152f8b6d374cacfac2c668c354423e (diff) | |
| download | bitbake-contrib-36fe8bae9fec61547ee0b13bcb721033afd3ac0e.tar.gz | |
knotty: display active tasks when printing keepAlive() message
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.
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit 30f6c3f175617beea8e8bb75dcf255611e3fc2fd)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
| -rw-r--r-- | lib/bb/ui/knotty.py | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/lib/bb/ui/knotty.py b/lib/bb/ui/knotty.py index e70c24640..71c5a3e9d 100644 --- a/lib/bb/ui/knotty.py +++ b/lib/bb/ui/knotty.py @@ -227,7 +227,9 @@ class TerminalFilter(object): def keepAlive(self, t): if not self.cuu: - print("Bitbake still alive (%ds)" % t) + print("Bitbake still alive (no events for %ds). Active tasks:" % t) + for t in self.helper.running_tasks: + print(t) sys.stdout.flush() def updateFooter(self): |