--disableUnreleasedIFRFlags doesn't exclude tests tagged with unreleased IFR tags when combined with --runAllFeatureFlagTests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running resmoke with --runAllFeatureFlagTests --disableUnreleasedIFRFlags, tests tagged with unreleased IFR feature flags are still selected to run, even though the flags are disabled on the server. This means the test executes against a server where the feature is off, leading to unexpected failures.

      See logs for update_cmd_mongos_slow_query_log.js running even though it was tagged with featureFlagUnifiedWriteExecutor which is currently an unreleasedIFRFlag

      This is also true for non passthrough tests. The following still runs lookup_unwind_sbe_pushdown.js even though the test is tagged with featureFlagSbeEqLookupUnwind which is a still an in development IFR flag.  

      buildscripts/resmoke.py run --suites=aggregation jstests/aggregation/sources/lookup/lookup_unwind_sbe_pushdown.js --runAllFeatureFlagTests --disableUnreleasedIFRFlags 

            Assignee:
            Alberto Massari
            Reporter:
            Erin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: