Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6867

Flaky: operation fails after two consecutive socket timeouts - aggregate on collection

    • Type: Icon: Build Failure Build Failure
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Flaky Test
    • 1
    • Not Needed
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      Unskip operation fails after two consecutive socket timeouts - aggregate on collection

      https://spruce.mongodb.com/task/mongo_node_driver_next_rhel80_large_node_latest_test_4.4_sharded_cluster_91d235221cc42a49bcfa85e428f83d8e6ba258d0_75c01e57abc470e785838d3c6dd0a8c0_25_03_18_15_22_09/logs?execution=0&sortBy=STATUS&sortDir=ASC

      [2025/03/18 11:43:50.198]   1) CSOT spec tests
      [2025/03/18 11:43:50.198]        legacy timeouts behave correctly for retryable operations
      [2025/03/18 11:43:50.198]          operation fails after two consecutive socket timeouts - aggregate on collection:
      [2025/03/18 11:43:50.198]      AssertionError: Operation aggregate succeeded but was not supposed to
      [2025/03/18 11:43:50.198]       at executeOperationAndCheck (test/tools/unified-spec-runner/operations.ts:1048:12)
      [2025/03/18 11:43:50.198]       at processTicksAndRejections (node:internal/process/task_queues:105:5)
      [2025/03/18 11:43:50.198]       at async runUnifiedTest (test/tools/unified-spec-runner/runner.ts:226:9)
      [2025/03/18 11:43:50.198]       at async Context.<anonymous> (test/tools/unified-spec-runner/runner.ts:336:13)
      

      User Experience

      • What is the desired/expected outcome for the user once this ticket is implemented?
      • If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

      Dependencies

      • upstream and/or downstream requirements and timelines to bear in mind

      Risks/Unknowns

      • What could go wrong while implementing this change? (e.g., performance, inadvertent behavioral changes in adjacent functionality, existing tech debt, etc)
      • Is there an opportunity for better cross-driver alignment or testing in this area?
      • Is there an opportunity to improve existing documentation on this subject?

      Acceptance Criteria

      Implementation Requirements

      • functional reqs, potential snafus to avoid, performance targets, etc

      Testing Requirements

      • unit test, spec test sync, etc

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow Up Requirements

      • additional tickets to file, required releases, etc
      • if node behavior differs/will differ from other drivers, confirm with dbx devs what standard to aim for and what plan, if any, exists to reconcile the diverging behavior moving forward

            Assignee:
            durran.jordan@mongodb.com Durran Jordan
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: