-
Petr Pudlak authored
Currently, when a job fails to starts, no error message is set, leading to "OpExecError: None". Since the function already receives a message in a ReasonElem, this patch: - extends the reason trail message with a description of the error that caused the job failure and - sets the message in the Op code result. Signed-off-by: Petr Pudlak <pudlak@google.com> Reviewed-by: Klaus Aehlig <aehlig@google.com>
a7ef9e77