[release/7.0] Don't re-use XmlSchemaSet - it's not threadsafe. #74564
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.
Backport of #74524 to release/7.0
/cc @karelz @StephenMolloy
Customer Impact
Blocks clean CI - test-only change.
Fixes #74370
These new tests use a few simple collections of schemas grouped in XmlSchemaSet. They were ported from NetFx, where apparently the test environment ran each test one at a time. (Seems that is also the case "on my machine" and in whatever pipelines were run to allow the tests to get checked in.) But XmlSchemaSet is not thread safe, so parallel execution of tests using a static XmlSchemaSet could be problematic. This change builds a new XmlSchemaSet per test instead of re-using a single instance.
Testing
CI
Risk
Low - test only change