delinquent_ops.js wall clock timer resolution drift could lead to test failure on windows

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • Fully Compatible
    • ALL
    • Workload Resilience 2026-05-11, Workload Resilience 2026-04-13
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      waitPerIterationMs and delinquentIntervalMs only have 20ms in difference, therefore there could be cases operations actually waited for waitPerIterationMs but the op wasn't counted in overdueInterruptChecks as the count is measured by wall clock and eventually lead to assert failures in delinquent_ops.js.

            Assignee:
            Jiaqi Tian
            Reporter:
            Jiaqi Tian
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: