Fix theoretical data race in transaction API test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding NYC 2023-01-23
    • 63
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Transaction API unit test DoesNotWaitForBestEffortAbortIfCancelled accesses an unsynchronized member variable in the test's mocked transaction API client, which triggered a TSAN failure. The access happens when the transaction API using the mocked client should be blocked on a condition variable, so there shouldn't be a problem in practice, but we should add synchronization to the mock class to silence TSAN and follow best concurrency practices.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: