[DRIVERS-2812] Address failing tests in Serverless Proxy incremental rollout Created: 22/Jan/24 Updated: 25/Jan/24 |
|
| Status: | Investigating |
| Project: | Drivers |
| Component/s: | Serverless |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Unknown |
| Reporter: | Steve Silvester | Assignee: | James Kovacs |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Driver Changes: | Not Needed | ||||||||||||||||
| Description |
SummaryIn DRIVERS-2648, we added our existing SDAM test to run against the Serverless Proxy, to confirm to the server team if their Serverless proxy is ready to roll out. Drivers adding those tests will see two SDAM failures in the following two tests: Drivers could work around this by skipping those two tests if testing on serverless incremental and blocking a fix on this ticket.
|
| Comments |
| Comment by Tom Selander [ 23/Jan/24 ] |
|
Triage: Need to mark this as dependent on the server ticket that was filed in response to the test failures that occurred as part of adding them in DRIVERS-2648. Once the server team addresses the issues/edge cases that were uncovered by our failing tests, we should pick this up to confirm that the tests are now passing. We will not plan on making changes to our tests, we just need to confirm that the serverless team has fixed their implementation to ensure that our driver tests are passing. tom.selander@mongodb.com to confirm that server ticket that this would be blocked on. |