[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: DisAgg testing runs the same test suite in a special DisAgg mode, so it’s important to separate warnings related to the regular codebase from those specific to DisAgg. The proposed approach is to first run the regular Python test suite with TSAN enabled, suppress any reported warnings, and then re-run the same tests in DisAgg mode. This has the indirect benefit of surfacing any new synchronization issues—even in the regular codebase—as CI failures, thereby improving test coverage.

Expected Impact: 

• Ability to separate DisAgg related and unrelated warnings
• Enhanced detection of synchronization issues in the regular codebase.