-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Quarantine some tests #26332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quarantine some tests #26332
Conversation
Hello @BrennanConroy! Because this pull request has the Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 60 minutes, a condition that will be fulfilled in about 46 minutes. No worries though, I will be back when the time is right! 😉 p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
@@ -422,13 +422,6 @@ public async Task ConfigurationTouchedStress_InProcess() | |||
await ConfigurationTouchedStress(HostingModel.InProcess); | |||
} | |||
|
|||
[ConditionalFact] | |||
[RequiresNewShim] | |||
public async Task ConfigurationTouchedStress_OutOfProcess() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @jkotalik
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah for out of proc this test wasn't really useful and just prone to flakiness. There are scenarios with out of proc that can still cause the app to return 502s during shutdown with out of proc. With inproc, it should be a guarantee.
#26331 and #26330