Consider raising timeout on TSAN noPassthrough evergreen task

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Correctness
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      While working on BF-30427, I identified and fixed a true data race, and filed tickets for the others. 

      However, I it was hard to reliably test the noPassthrough task without hitting the timeout, and I raised the timeout to 3 hours for the duration of my testing, which I found allowed the tests to reliably complete under the time limit. I think it may be worthwhile to permanently increase this time limit in order to reduce the flakiness of the TSAN testing.

            Assignee:
            Unassigned
            Reporter:
            Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: