Actions
Feature #8466
closedImprove error messages when Native Scheduler terminates jobs because of reached computational resource limits
Start date:
09/29/2017
Due date:
% Done:
0%
Estimated time:
Published in build:
Description
For instance, in case of outs of memory there is such the error message for the Corrupted status:
Execution of job caf96491839144a5566b4145e95df133 terminated with an exception: Execution of job caf96491839144a5566b4145e95df133 finished with non-zero exit code: 9
that doesn't explain well what happened and what users should to do.
Moreover, I would like to see special statuses in such the cases since Corrupted is a special status reflecting some issues within Core and its components. But in case of reaching computational resource limits there can be no such issues.
Actions