noop_drop.js override is never applied in parallel shells due to a typo'd import path

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • RSSD
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Overview

      The noop_drop.js override registers itself in parallel shells with a misspelled path, so the override is never applied in any parallel shell spawned by tests running under the magic_restore passthrough suites.

      Details

      jstests/libs/override_methods/noop_drop.js, line 25:

      OverrideHelpers.prependOverrideInParallelShell("jstesats/libs/override_methods/noop_drop.js");
      

      "jstesats" should be "jstests". OverrideHelpers.prependOverrideInParallelShell prepends await import("[path]") to every startParallelShell body, so any test spawning a parallel shell gets a failing module import instead of the noop-drop override.

      The typo dates back to the file's introduction (SERVER-89647, commit 34a2d0d2e06).

      Affected Suites

      • magic_restore_replica_sets_jscore_passthrough.yml
      • magic_restore_sharded_collections_jscore_passthrough.yml
      • magic_restore_sharding_jscore_passthrough.yml

      Suggested Fix

      Fix the path typo and verify that parallel-shell tests in the three suites still pass with the override actually applied (drops becoming no-ops in parallel shells may surface latent test issues).

            Assignee:
            Unassigned
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: