Quarantine flaky test WithHttpCommand_UsesNamedHttpClient #9802
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 PR quarantines the flaky test
Aspire.Hosting.Tests.WithHttpCommandTests.WithHttpCommand_UsesNamedHttpClient
by adding the[QuarantinedTest]
attribute.Changes Made
[QuarantinedTest("https://github.com/dotnet/aspire/issues/9800")]
attribute to theWithHttpCommand_UsesNamedHttpClient
test methodtests-outerloop.yml
) instead of the regular tests workflow (tests.yml
)Background
The
QuarantinedTest
attribute is used to mark tests that are flaky and don't fail deterministically. These tests are excluded from regular CI runs to prevent false failures, but are still executed in the outerloop workflow to monitor their behavior.The attribute follows the established pattern used by other quarantined tests in the same file and references the GitHub issue tracking the underlying flakiness.
Fixes #9801.