From Ivan

But for DisAgg, I think it would be more productive to simply collect all the warnings that were already there before the DisAgg merge and then share all DisAgg-related warnings across the Storage Engines teams. This might require implementing a custom TSAN warning-suppression tool, since TSAN only supports function/file-level suppressions—and a single function might have both DisAgg-related and unrelated warnings. But that’s an implementation detail.

Personally, I think enabling regular TSAN testing for the DisAgg tests would be a major improvement to our test infrastructure. It would significantly increase data race detection coverage for new code and allow us to catch synchronization issues on the fly as development continues.

The work here is to create a custom TSAN suppression that will collect all warnings in classic WT and then in Disagg WT and suppress them line by line. By doing so, we can capture new TSAN warnings and have effective TSAN instrumentation for both classic and disagg world.