pegasus-analyzer should be able to handle cases where the workflow failed to start

XMLWordPrintable

      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.

            Assignee:
            Karan Vahi
            Reporter:
            Gideon Juve (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: