PM-704 We send a db job end event in case of prescript failure to
ensure that the associated job instance gets associated with the
prescript failure exitcode. This ensures, that the job appears failed
on presript failures.
PM-704 we now determine the planner pre script log file ( the rotated
one ) in case of prescript failures and store it in the database for
the dax job as the stdout file. Added prescript to the job_info
dictionary in the workflow class.
PM-704 for prescript failures we now store the contents of planner
prescript invocation log.
PM-704 the read_stdout_stderr function did not have a circuit breaker
for exceeding the MAX_OUTPUT_LENGTH
PM-704 we want the prescript invocation status to be taken into account for hte
job instance statistics files. this is for the case where the
prescripts for the dax jobs fail. we want the pre script status to be displayed.
PM-704 in case of prescript failure only we have to update the job
output counter to handle planner prescript rotated logs. We cannot do
it at PRE_SCRIPT_STARTED event because then update happens both for
pre script started and the submit event for the same sub workflow job!
PM-704 monitord.subworkflow.db was not rotated in case of replay or
recover case. that put the workflow retries off.
Also the workflow retries are now solely updated based on the job
counters. Pre script failures increment the job counters.
Merge branch 'PM-704' into 4.2