Test | Add lock when using ClearSqlConnectionGlobalProviders #1461
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.
s_globalCustomColumnEncryptionKeyStoreProviderscan only be set once usingSqlConnection.RegisterColumnEncryptionKeyStoreProviders(). It has to be cleared after any test sets it, so that other tests can set it again. Because the functional tests run in parallel, we sometimes see aKey store providers cannot be set more than once.error. We can add a lock to ensure only one test at a time is setting and clearings_globalCustomColumnEncryptionKeyStoreProviders.Repro:
https://github.com/johnnypham/SqlClient/tree/testfailurerepro
Run the two tests with the appropriate filter: