-
Type:
Build Failure
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Go Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Name of Failure:
TestClientStress/Client_recovers_from_traffic_spike/maxPoolSize_100
Link to task:
Context of when and why the failure occurred:
Intermittent failure
Stack trace:
[2024/09/18 10:15:16.961] === RUN TestClientStress/Client_recovers_from_traffic_spike/maxPoolSize_1
[2024/09/18 10:15:16.961] client_test.go:1090: Max RTT 2.0935ms; using a timeout of 209.35ms
[2024/09/18 10:15:16.961] client_test.go:1114: Error from extreme traffic spike (errors are expected): connection(localhost:27017[-2273]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52777->[::1]:27017: i/o timeout
[2024/09/18 10:15:16.961] client_test.go:1076: Connections created: 10, connections closed: 8, pool clears: 0
[2024/09/18 10:15:16.961] === RUN TestClientStress/Client_recovers_from_traffic_spike/maxPoolSize_10
[2024/09/18 10:15:16.961] client_test.go:1090: Max RTT 2.0935ms; using a timeout of 209.35ms
[2024/09/18 10:15:16.961] client_test.go:1114: Error from extreme traffic spike (errors are expected): remaining time -657.7µs until context deadline is less than or equal to min network round-trip time 0s (network round-trip time stats: moving avg: 343.28µs, min: 0s): operation not sent to server, as Timeout would be exceeded: context deadline exceeded
[2024/09/18 10:15:16.961] client_test.go:1076: Connections created: 21, connections closed: 1, pool clears: 0
[2024/09/18 10:15:16.961] === RUN TestClientStress/Client_recovers_from_traffic_spike/maxPoolSize_100
[2024/09/18 10:15:16.961] client_test.go:1090: Max RTT 2.0935ms; using a timeout of 209.35ms
[2024/09/18 10:15:16.961] client_test.go:1114: Error from extreme traffic spike (errors are expected): connection(localhost:27018[-2412]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52978->[::1]:27018: i/o timeout
[2024/09/18 10:15:16.961] client_test.go:1122:
[2024/09/18 10:15:16.961] Error Trace: C:\data\mci\9b67dfbd99dbb23218cfd51c2bca2b95\src\go.mongodb.org\mongo-driver\internal\integration\client_test.go:1122
[2024/09/18 10:15:16.961] C:\data\mci\9b67dfbd99dbb23218cfd51c2bca2b95\src\go.mongodb.org\mongo-driver\internal\integration\mongotest.go:268
[2024/09/18 10:15:16.961] Error: Should be true
[2024/09/18 10:15:16.961] Test: TestClientStress/Client_recovers_from_traffic_spike/maxPoolSize_100
[2024/09/18 10:15:16.961] Messages: expected no errors, but got 5 ([connection(localhost:27018[-2460]) incomplete read of message header: context deadline exceeded: read tcp [::1]:53023->[::1]:27018: i/o timeout connection(localhost:27018[-2394]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52962->[::1]:27018: i/o timeout connection(localhost:27017[-2326]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52884->[::1]:27017: i/o timeout connection(localhost:27018[-2394]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52962->[::1]:27018: i/o timeout connection(localhost:27017[-2326]) incomplete read of message header: context deadline exceeded: read tcp [::1]:52884->[::1]:27017: i/o timeout])
[2024/09/18 10:15:16.961] client_test.go:1076: Connections created: 201, connections closed: 1, pool clears: 0