This repository was archived by the owner on Jan 23, 2023. It is now read-only.
[release/3.1] Corresponding unit tests for dotnet/coreclr#28014 - #42862
Merged
Conversation
GrabYourPitchforks
added
area-System.Runtime
Servicing-approved
Member
|
https://dev.azure.com/dnceng/internal/_build/results?buildId=526518 is the build that contains the CoreClr change, we can re-run this after we ingest that build |
Member
|
Here's the PR ingesting the CoreClr change: #42865 We should re-run CI after that's merged |
Member
Author
|
These are just unit tests - there's no behavioral change as part of this PR. It's ok if this PR slips past the 3.1.3 checkin deadline. |
Member
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
These are the unit tests for dotnet/coreclr#28014, which is a customer-reported infinite loop in
string.Replace.The unit tests will fail (by entering an infinite loop) until that PR is checked in to coreclr and the corresponding build flows to corefx.