summaryrefslogtreecommitdiffstats
path: root/scripts/lib/devtool/export.py
diff options
context:
space:
mode:
authorRoss Burton <ross@burtonini.com>2022-04-29 19:15:37 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-04-30 07:33:59 +0100
commit638c8860eba17b97b66649333e0c94e47d7f0002 (patch)
tree4d618ca918b183aa613f42db9fe08b9f51fa8d0b /scripts/lib/devtool/export.py
parent99e1aff4ba4380a8ea938adabb8d22f5e4c34559 (diff)
downloadpoky-638c8860eba17b97b66649333e0c94e47d7f0002.tar.gz
bitbake: 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. (Bitbake rev: cc4e7d7049f949b54b1ea7926844b3c76f361c64) 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>
Diffstat (limited to 'scripts/lib/devtool/export.py')
0 files changed, 0 insertions, 0 deletions