Create a triage process for our TSAN warnings

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Not Applicable
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - Q3+ Backlog
    • None

      [That is the part of our deliverables for the TSAN project for Q3. This is an umbrella ticket that could be split to finer-grained ones if needed.]

      Context: As we plan to distribute the responsibility for investigating and resolving newly reported issues across multiple teams, it would be beneficial to provide a reference document. This document should clearly outline the steps for:

      1. Investigating the root cause of a TSAN warning

      2. Determining whether the warning is a true or false positive

      3. Validating and proving the correctness of a proposed fix

      Expected Impact: Enable developers to effectively investigate and resolve newly reported synchronization issues.

              Assignee:
              [DO NOT USE] Backlog - Storage Engines Team
              Reporter:
              Ivan Kochin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: