summaryrefslogtreecommitdiffstats
path: root/bitbake
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2022-03-27 06:44:00 -1000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2022-03-28 13:30:50 +0100
commit7616c4935578a0699149da8a482ad81bd98bdd08 (patch)
tree8b77d7327f87e7dcbf21f3188a26683876432161 /bitbake
parent8183149d3e06375e0453e52a85aabb1f8b27f701 (diff)
downloadpoky-7616c4935578a0699149da8a482ad81bd98bdd08.tar.gz
bitbake: server/process: Note when commands complete in logs
Its hard to tell from the server logs whether commands complete or not (or how long they take). Add extra info to allow more debugging of server timeouts. (Bitbake rev: d388f6d159b9d7e1ed3f199f2d1aca0c473cda6d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 56285ada585ec1481449522282b335bcb5a2671e) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake')
-rw-r--r--bitbake/lib/bb/server/process.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/bitbake/lib/bb/server/process.py b/bitbake/lib/bb/server/process.py
index 7b13576274..3c9ed70689 100644
--- a/bitbake/lib/bb/server/process.py
+++ b/bitbake/lib/bb/server/process.py
@@ -221,6 +221,7 @@ class ProcessServer(multiprocessing.Process):
221 try: 221 try:
222 print("Running command %s" % command) 222 print("Running command %s" % command)
223 self.command_channel_reply.send(self.cooker.command.runCommand(command)) 223 self.command_channel_reply.send(self.cooker.command.runCommand(command))
224 print("Command Completed")
224 except Exception as e: 225 except Exception as e:
225 logger.exception('Exception in server main event loop running command %s (%s)' % (command, str(e))) 226 logger.exception('Exception in server main event loop running command %s (%s)' % (command, str(e)))
226 227