mongo-task-generator should use historical data from master when unavailable on current version

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • 135
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      https://jira.mongodb.org/browse/BF-30753 This BF was caused because when we branched the mongo-task-generator failed to find historical data for this suite and the default timeout was too low.

       

      mikhail.shchatko@mongodb.com do you know if there was a DAG ticket already tracking this?

            Assignee:
            Unassigned
            Reporter:
            Trevor Guidry
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: