-
Notifications
You must be signed in to change notification settings - Fork 753
Closed
Labels
area-engineering-systemsinfrastructure helix infra engineering repo stuffinfrastructure helix infra engineering repo stuffcopilot-taskIssue to assign a task to CopilotIssue to assign a task to Copilot
Description
Task
Quarantine flaky test(s):
Tests to quarantine:
- Test: Aspire.Cli.Tests.Commands.PublishCommandTests.PublishCommandSucceedsEndToEnd
Issue:Failing test: Aspire.Cli.Tests.Commands.PublishCommandTests.PublishCommandSucceedsEndToEnd #9870
Background for Quarantined tests
- Tests that are flaky and don't fail deterministically are marked with the
QuarantinedTestattribute. The full type name for this isAspire.TestUtilities.QuarantinedTest. - Such tests are not run as part of the regular tests workflow (
tests.yml).- Instead they are run in the
Outerloopworkflow (tests-outerloop.yml).
- Instead they are run in the
- The
QuarantinedTestattribute takes an optional reason parameter, typically a GitHub issue URL - The pattern is consistent:
[QuarantinedTest("https://github.com/dotnet/aspire/issues/XXXXX")] - The attribute is placed right before the test method, after
[Fact]or other test attributes - Tests are quarantined by adding this attribute, which makes them run in the outerloop workflow instead of regular tests
Note that this issue is only to track the task of quarantining the flaky test. And the issue url mentioned here is the real issue to be used with the QuarantinedTest attribute. So, close only this issue.
Copilot
Metadata
Metadata
Assignees
Labels
area-engineering-systemsinfrastructure helix infra engineering repo stuffinfrastructure helix infra engineering repo stuffcopilot-taskIssue to assign a task to CopilotIssue to assign a task to Copilot