Do not set dynamic timeouts on tasks with tests that have no runtime history

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • v5.0
    • DAG 2021-09-06
    • 26
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When determining dynamic task timeouts, there is a case where a test may not have passed during our lookback window (2 weeks), but was run and still has a history. In this case, the reported runtime of the task looks like 0. If we hit this case, we should skip applying the dynamic timeout, since a runtime of 0 is inaccurate and we don't know what the actual runtime is.

              Assignee:
              David Bradford (Inactive)
              Reporter:
              David Bradford (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: