ExportXMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Foundations
    • 131.352
    • None
    • None
    • Close concurrency testing gaps in WT testing

      Description

      WT already runs many tests without TSAN that are missing, disabled, or run with reduced coverage under TSAN. This leaves concurrency problems in those workloads outside our TSAN testing.

      Close those gaps so that the testing we run under TSAN covers the same behaviours as our non-TSAN testing. Where a test or workload cannot reasonably run under TSAN, record the reason in one common place.

      This is about gaps relative to non-TSAN testing, not adding new tests or expanding both kinds of testing. Compare classic WT with classic WT, and disagg with the corresponding non-TSAN disagg configuration.

      Confirmed gaps

      Area Gap compared with non-TSAN testing Existing or proposed work
      Python tests tsan.fail excludes 61 test files, and there are additional TSAN-only skips inside tests. The fail-list header says most reasons are unknown. Review the exclusions and re-enable tests or explain why they remain excluded. Reuse WT-14098 for checkpoint33.
      test/format TSAN uses separate jobs with smaller workloads. The larger TSAN passes use 100,000–300,000 rows and 1–3 tables, versus 1,000,000–5,000,000 rows and 3–10 tables in CONFIG.stress. The common disagg stress tag is not enabled on the TSAN variants. WT-16309; compare the remaining modes and workload settings in the common plan.
      Lock-order deadlock detection Larger format runs and several Python TSAN jobs set detect_deadlocks=0 because of a sanitizer runtime failure. Only the small format passes retain it. WT-16313.
      test/model Ordinary CI has unit tests, saved failure workloads, long/random-config workloads, and disagg workloads. These are not selected on the two WT TSAN variants. Enable existing model tests under TSAN.
      C suite TSAN runs a disagg schema-abort smoke task, but not the ordinary fast/long C-suite coverage. Run the missing C-suite tests under TSAN.
      C++ suite The WT TSAN variants do not select the ordinary cppsuite-* functional/stress tasks. Run the missing C++ suite tests under TSAN.
      Catch2 The WT TSAN variants select neither a dedicated Catch2 task nor make-check-test. Run the existing Catch2 tests under TSAN.
      Standalone checkpoint tests Ordinary checkpoint test/stress workloads are not selected on the WT TSAN variants. Python checkpoint tests are not the same workload. Run the missing standalone checkpoint tests under TSAN.

      TBD

      Do an analysis of how many issues we've already missed because of not having this testing coverage.

      Done when

      • Every existing non-TSAN workload in the agreed plan has TSAN coverage or a recorded reason for exclusion.
      • The known Python, format, missing-suite, and deadlock-detection gaps are addressed or explained.
      • The weekly (AI based??) checks flags new unexplained coverage gaps.

            Assignee:
            Unassigned
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: