This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Delete bad test from AsyncValueTaskMethodBuilderTests #23356
Merged
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.
This test was failing on uapaot (https://github.com/dotnet/corefx/issues/22545). It turns out that the behavior it depends on was explicitly disabled in Release builds of S.P.CoreLib (see the issue for details).
Per @stephentoub, this test was added only to increase code coverage, and the machinery it depends on is being removed in CoreCLR soon too (dotnet/coreclr#13105). With that in mind, we feel it's pretty safe to just delete the test.
@stephentoub PTAL
Fixes https://github.com/dotnet/corefx/issues/22545