Exclusion plugin does not handle a single job listing same resource multiple times

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • Component/s: exclusion-plugin
    • None

      It's not entirely clear if this should work, but seems like it should be detected as a deadlock if job X #Y is waiting on resource held by job X #Y.

            Assignee:
            Unassigned
            Reporter:
            Nathan Neulinger
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: