Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-62637

Find a way to avoid running shardMerge js tests for community build variants.

    • Type: Icon: Task Task
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Serverless
    • Server Serverless 2023-01-23, Server Serverless 2023-02-06, Server Serverless 2023-02-20, Server Serverless 2023-03-06, Server Serverless 2023-03-20, Server Serverless 2023-04-03, Server Serverless 2023-04-17

      Our shard Merge implementation + it's related unit & js tests are located in the community repo but depends on enterprise-only feature, like, backup cursor. If we run those tests on a non-enterprise build variant, those tests would fail.

      Currently the shard Merge implementation is behind a feature flag. And, we run all feature flags enabled only on enterprise-only build variants. However, we are safe now as we don't run shard merge tests on non-enterprise build variant. But, once we enable the shardMerge flag, we would start seeing test failures w/ error message -

       "Unrecognized pipeline stage name: '$backupCursor'" 

            Assignee:
            suganthi.mani@mongodb.com Suganthi Mani
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: