Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82601

Consider raising timeout on TSAN noPassthrough evergreen task

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Correctness

    Description

      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.

      Attachments

        Activity

          People

            devprod-correctness-team@mongodb.com [DO NOT ASSIGN] Backlog - DevProd Correctness
            erin.mcnulty@mongodb.com Erin McNulty
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: