DRIVERS-3390 Add appName to OIDC test failpoints#1891
Merged
kevinAlbs merged 3 commits intomongodb:masterfrom Feb 6, 2026
Merged
DRIVERS-3390 Add appName to OIDC test failpoints#1891kevinAlbs merged 3 commits intomongodb:masterfrom
kevinAlbs merged 3 commits intomongodb:masterfrom
Conversation
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
appNameto isolate failpoints in OIDC tests.Background & Motivation
This is intended to address test failures observed in C (example) and Rust (example), and maybe others drivers. Sometimes the GCP OIDC tests fail to trigger an expected failpoint.
Running repeatedly in the C driver reproduced the failure on a test configuring a failpoint. This patch build logs:
The "find" did not expectedly fail.
Diagnosing
Using
mongoshto connect to an Atlas cluster created by the OIDC GCP scripts enabled testing a failpoint in the same environment:This usually throws the expected exception. However, if paused between configuring the failpoint and running the
findcommand, thefindsometimes surprisingly succeeds.Printing server logs indicate the automation agent is connecting:
So I expect another process may be triggering the failpoint.
Testing
With the
appNameadded, a test of the C driver running on repeat 20 times passes:Evergreen patch: https://spruce.mongodb.com/version/6983ff9b967f4f00073726da
Please complete the following before merging:
[ ] Update changelog.N/A. Test changes only.[ ] Test these changes against all server versions and topologies (including standalone, replica set, and shardedN/A. Tested OIDC tasks.clusters).