Reset FCV at end of random_ddl_setFCV_operations_with_metadata_check.js

XMLWordPrintableJSON

    • Query Execution
    • Fully Compatible
    • ALL
    • v8.0
    • QE 2025-06-09
    • 200
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The FSM concurrency test jstests/concurrency/fsm_workloads/ddl/random_ddl/random_ddl_setFCV_operations_with_metadata_check.js modifies the FCV by calling setFCV with different FCV versions.
      When the test completes, it currently does not reset the setFCV to latest in its teardown function.
      This means that all following fsm concurrency tests run with a non-deterministic version, which can make some of them fail that rely on FCV-gated feature flags.

      This is at least true for some timeseries fsm concurrency tests, which rely on the FCV-gated feature flag gTimeseriesSupportsUpdate and these currently fail non-deterministically, depending on the order in which the fsm concurrency tests are executed.

      This caused BF-37996.

            Assignee:
            Jan Steemann
            Reporter:
            Jan Steemann
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: