bitbake: cooker: pass exception to finishAsyncCommand
An invalid task causes bitbake to exit incorrectly, firing a CommandCompleted event rather than a CommandFailed one. This means that clients listening for CommandFailed events are unable to detect the build failure even though one occurred. Passing an exception string to finishAsyncCommand when a task fails causes the CommandFailed event to be fired correctly. [YOCTO #9087] (Bitbake rev: 98a2c37e077b16e3bc8bb102bd18b293130d15a4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
ffa2ca007f
commit
1131303ec4
|
@ -1349,7 +1349,7 @@ class BBCooker:
|
|||
failures += len(exc.args)
|
||||
retval = False
|
||||
except SystemExit as exc:
|
||||
self.command.finishAsyncCommand()
|
||||
self.command.finishAsyncCommand(str(exc))
|
||||
return False
|
||||
|
||||
if not retval:
|
||||
|
@ -1385,7 +1385,7 @@ class BBCooker:
|
|||
failures += len(exc.args)
|
||||
retval = False
|
||||
except SystemExit as exc:
|
||||
self.command.finishAsyncCommand()
|
||||
self.command.finishAsyncCommand(str(exc))
|
||||
return False
|
||||
|
||||
if not retval:
|
||||
|
|
Loading…
Reference in New Issue