Delete flaky test MultipleThreadsForceRefresh #55290
Open
+0
−70
Conversation
This file contains 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
I added it to do manual validation and kept it when it seemed to be stable. To make it properly stable, we'd have to add a special test hook to let us manipulate lock usage, which doesn't seem worthwhile for the marginal coverage the test provides. Fixes dotnet#55227
|
I claim deleting this data protection test didn't break a bunch of MVC tests |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
wtgodbe
approved these changes
Apr 30, 2024
|
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
dotnet-policy-service
bot
added
the
pending-ci-rerun
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.
I added it to do manual validation and kept it when it seemed to be stable. To make it properly stable, we'd have to add a special test hook to let us manipulate lock usage, which doesn't seem worthwhile for the marginal coverage the test provides.
Fixes #55227