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

Flaky: CSOT spec test: operation succeeds after one socket timeout - listDatabases on client [1]

XMLWordPrintableJSON

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

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

      might be related to NODE-6787

      [2025/03/12 17:01:15.244]   1) CSOT spec tests
[2025/03/12 17:01:15.244]        legacy timeouts behave correctly for retryable operations
[2025/03/12 17:01:15.244]          operation succeeds after one socket timeout - listDatabases on client:
[2025/03/12 17:01:15.244]      AssertionError: Expected event count mismatch, expected [ 'commandStartedEvent', 'commandStartedEvent' ] but got [ 'CommandStartedEvent' ]
[2025/03/12 17:01:15.244]       at failOnMismatchedCount (test/tools/unified-spec-runner/match.ts:447:10)
[2025/03/12 17:01:15.244]       at matchesEvents (test/tools/unified-spec-runner/match.ts:685:7)
[2025/03/12 17:01:15.244]       at runUnifiedTest (test/tools/unified-spec-runner/runner.ts:250:22)
[2025/03/12 17:01:15.244]       at processTicksAndRejections (node:internal/process/task_queues:105:5)
[2025/03/12 17:01:15.244]       at async Context.<anonymous> (test/tools/unified-spec-runner/runner.ts:336:13)

            Assignee:
            Unassigned Unassigned
            Reporter:
            daria.pardue@mongodb.com Daria Pardue
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None