DRIVERS-3106 note cryptSharedLibPath may be set by test runner
#1817
Conversation
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
baileympearson
approved these changes
Jul 15, 2025
mdb-ad
approved these changes
Jul 15, 2025
alcaeus
approved these changes
Jul 17, 2025
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
Note
cryptSharedLibPathmay be set by test runner if not present.Background & Motivation
Motivated by this slack conversation. Passing an explicit path to
crypt_sharedin the test runner may avoid test errors loading crypt_shared from two different paths if other tests are passing an explicitcryptSharedLibPath. WhencryptSharedLibPathis not passed, libmongocrypt may rely on the system library loader (which may load from the working directory or system directories).Please complete the following before merging:
cryptSharedLibPathif not present mongo-c-driver#2060[ ] Test these changes against all server versions and topologies (including standalone, replica set, and shardedC does not currently test In-Use Encryption with sharded.clusters).