-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major
-
Affects Version/s: 4.5.3
-
Component/s: statistics visualization and debugging tools
-
None
I have had 3 cases in the last two weeks where a workflow failed to start and pegasus-analyzer responded with a useless stack trace. These were related to PM-1039 and PM-972.
pegasus-analyzer should be able to detect that the workflow didn't start, and look in the dag.dagman.out and dag.lib.
{out,err}to determine a cause.