jobs aborted by dagman, but with kickstart exitcode as 0 are not marked as failed job

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical
    • master, 5.1.0, 5.0.1
    • Affects Version/s: master, 5.0.1
    • Component/s: None
    • None

      I've created a workflow that is expected to fail because an expected job output file is not produced. When using `pegasus.mode=development`, I observe a held task when watching p-status output. After less than a minute, the held task goes away and the workflow runs to completion. p-analyzer output also shows 100% complete.

      The expected behavior would be that the workflow fails right away.

        1. run0001.tar.gz
          49 kB
        2. Screen Shot 2021-04-13 at 11.37.24 AM.png
          Screen Shot 2021-04-13 at 11.37.24 AM.png
          98 kB
        3. wf.py
          1 kB

            Assignee:
            Karan Vahi
            Reporter:
            Ryan Tanaka [X] (Inactive)
            Archiver:
            Rajiv Mayani

              Created:
              Updated:
              Resolved:
              Archived: