[GODRIVER-2945] Fix Failing Serverless Builds Created: 15/Aug/23  Updated: 27/Oct/23  Resolved: 29/Aug/23

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Build Failure Priority: Unknown
Reporter: Steve Silvester Assignee: Steve Silvester
Resolution: Gone away Votes: 0
Labels: greenerbuild
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-80291 Serverless Proxy is returning 8000 er... Closed
is related to PYTHON-3891 Several Failing Tests on Serverless T... Closed
Documentation Changes Summary:

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?


 Description   

Several serverless tests related to retryable reads are failing. This appears to be consistent for the Python and Node drivers. We might need to prioritize DRIVERS-1869

https://spruce.mongodb.com/task/mongo_go_driver_serverless__os_serverless~ubuntu2204_go_1_20_test_serverless_patch_d6bd0d73ba4761b45c8687940affe6d6002bfa59_64dac7815623433787896399_23_08_15_00_32_02/tests?execution=0&sortBy=STATUS&sortDir=ASC

 [2023/08/15 00:44:08.457] === RUN   TestUnifiedSpecs/retryable-reads/aggregate.json
 [2023/08/15 00:44:08.457] === RUN   TestUnifiedSpecs/retryable-reads/aggregate.json/Aggregate_succeeds_on_first_attempt
 [2023/08/15 00:44:08.457] === RUN   TestUnifiedSpecs/retryable-reads/aggregate.json/Aggregate_succeeds_on_second_attempt
 [2023/08/15 00:44:08.457]     unified_spec_test.go:336:
 [2023/08/15 00:44:08.457]         	Error Trace:	/data/mci/a2df933ec328505a8037712ce9ba5094/src/go.mongodb.org/mongo-driver/mongo/integration/unified_spec_test.go:336
 [2023/08/15 00:44:08.457]         	            				/data/mci/a2df933ec328505a8037712ce9ba5094/src/go.mongodb.org/mongo-driver/mongo/integration/mongotest.go:266
 [2023/08/15 00:44:08.457]         	Error:      	Expected nil, but got: &errors.errorString{s:"did not expect error but got (AtlasError) closed connection due to 'failCommand' failpoint"}
 [2023/08/15 00:44:08.457]         	Test:       	TestUnifiedSpecs/retryable-reads/aggregate.json/Aggregate_succeeds_on_second_attempt
 [2023/08/15 00:44:08.457]         	Messages:   	error running operation "aggregate" at index 0: did not expect error but got (AtlasError) closed connection due to 'failCommand' failpoint
 [2023/08/15 00:44:08.457]     unified_spec_test.go:345:
 [2023/08/15 00:44:08.457]         	Error Trace:	/data/mci/a2df933ec328505a8037712ce9ba5094/src/go.mongodb.org/mongo-driver/mongo/integration/cmd_monitoring_helpers_test.go:269
 [2023/08/15 00:44:08.457]         	            				/data/mci/a2df933ec328505a8037712ce9ba5094/src/go.mongodb.org/mongo-driver/mongo/integration/unified_spec_test.go:345
 [2023/08/15 00:44:08.457]         	            				/data/mci/a2df933ec328505a8037712ce9ba5094/src/go.mongodb.org/mongo-driver/mongo/integration/mongotest.go:266
 [2023/08/15 00:44:08.457]         	Error:      	Expected nil, but got: &errors.errorString{s:"expected CommandStartedEvent, got nil"}
 [2023/08/15 00:44:08.457]         	Test:       	TestUnifiedSpecs/retryable-reads/aggregate.json/Aggregate_succeeds_on_second_attempt
 [2023/08/15 00:44:08.457]         	Messages:   	expectation comparison error at index 1: expected CommandStartedEvent, got nil



 Comments   
Comment by Steve Silvester [ 29/Aug/23 ]

Builds are passing now: https://spruce.mongodb.com/task/mongo_go_driver_serverless__os_serverless~ubuntu2204_go_1_20_test_serverless_67f257ac1d970452575fa24d7394e1ed46d1d725_23_08_24_01_33_26/logs?execution=3&sortBy=STATUS&sortDir=ASC

Comment by Steve Silvester [ 15/Aug/23 ]

Example node failure: https://spruce.mongodb.com/task/mongo_node_driver_next_rhel8_test_serverless_test_serverless_patch_1e96e49b607791d1c1517e65cf88f51821898b0b_64da95b50ae60688ec805957_23_08_14_20_59_33?execution=0&sortBy=STATUS&sortDir=ASC

Generated at Thu Feb 08 08:39:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.