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>
failures += len(exc.args)
retval = False
except SystemExit as exc:
- self.command.finishAsyncCommand()
+ self.command.finishAsyncCommand(str(exc))
return False
if not retval:
failures += len(exc.args)
retval = False
except SystemExit as exc:
- self.command.finishAsyncCommand()
+ self.command.finishAsyncCommand(str(exc))
return False
if not retval: