From ad09c355d13498639fd00b951100d7324938fea5 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Mon, 10 Mar 2025 14:56:38 +0000 Subject: [PATCH] bitbake: command: Fix command complete event ordering The command complete event triggers the UI to start new commands. We should send this once we've cleaned up existing commands since on very slow systems, this could otherwise cause failures. There is a 30s timeout on incomming commands but slow systems have been known to hit this on poorly configured I setups. (Bitbake rev: d202298b3d989c39bc532b69c410e2e78b082a11) Signed-off-by: Richard Purdie --- bitbake/lib/bb/command.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bitbake/lib/bb/command.py b/bitbake/lib/bb/command.py index baa7cbade1..59a979ee90 100644 --- a/bitbake/lib/bb/command.py +++ b/bitbake/lib/bb/command.py @@ -143,14 +143,14 @@ class Command: return bb.server.process.idleFinish(traceback.format_exc()) def finishAsyncCommand(self, msg=None, code=None): + self.cooker.finishcommand() + self.process_server.clear_async_cmd() if msg or msg == "": bb.event.fire(CommandFailed(msg), self.cooker.data) elif code: bb.event.fire(CommandExit(code), self.cooker.data) else: bb.event.fire(CommandCompleted(), self.cooker.data) - self.cooker.finishcommand() - self.process_server.clear_async_cmd() def reset(self): if self.remotedatastores: