Add does_not_support_stepdowns tag to explain_includes_command.js

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • QO 2025-02-17
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Problem

      The test jstests/core/query/explain/explain_includes_command.js is missing the does_not_support_stepdowns tag that all other explain tests in the same directory have. When this test runs in a stepdown passthrough suite (e.g., sharding_kill_stepdown_terminate_jscore_passthrough), the config server primary is killed, causing {{db.runCommand(

      {explain: ...}

      )}} to return {{

      {ok: 0}

      }} with a "could not get updated shard list" timeout error. The subsequent assertion assert("command" in explainOutput) fails, and the shell exits with code -3.

      Evidence* BF-45241 tracks the build failure

      • Test log shows: "errmsg" : "could not get updated shard list from config server :: caused by :: Request timed out"
      • Shell exit code 4294967293 (unsigned -3, indicating uncaught JS exception)

      Scope of Work

      • jstests/core/query/explain/explain_includes_command.js — add does_not_support_stepdowns to the @tags list

      Acceptance Criteria

      • The test is excluded from stepdown passthrough suites
      • The test still runs in non-stepdown suites

            Assignee:
            Jess Balint
            Reporter:
            Jess Balint
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: