test-bson-latest-driver-7.0.0 is failing due to the broken test

XMLWordPrintableJSON

    • Type: Build Failure
    • Resolution: Duplicate
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • Not Needed
    • None
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      The configuration for the task:

      - name: test-bson-latest-driver-7.0.0-server-tests
    commands:
      - command: expansions.update
        type: setup
        params:
          updates:
            - { key: VERSION, value: latest }
            - { key: TOPOLOGY, value: server }
            - { key: AUTH, value: auth }
            - { key: SSL, value: nossl }
            - { key: CLIENT_ENCRYPTION, value: "false" }
            - { key: NODE_LTS_VERSION, value: "20.19.0" }
      - func: install dependencies
        vars:
          NPM_VERSION: "11.11.1"
      - func: bootstrap mongo-orchestration
      - func: switch source
        vars:
          SOURCE_REV: refs/tags/v7.0.0
      - func: install package
        vars:
          PACKAGE: https://github.com/mongodb/js-bson#HEAD
      - func: log state
      - func: run tests

      https://spruce.corp.mongodb.com/task/mongo_node_driver_next_BSON_compatibility_tests_test_bson_latest_driver_7.0.0_sharded_cluster_tests_1fc0e09f0c7b06508030810cd65b5998c999f96c_26_04_14_15_00_12/logs?execution=0

      It means that we always run tests from the tag v7.0.0. Recent update in mongodb (v9.0) made one test failing ("regression test (NODE-6878)"), and even though the test is fixed now on main it will always fail on subsequent runs (on PRs as well as on main) because it always takes old code.

      AC:

      • investigate the problem, and document the solution where we can get both: solution for original NODE-7400 which added this task but also enough robustness to get CI green

            Assignee:
            Unassigned
            Reporter:
            Sergey Zelenov
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: