Quarantine RustPolyglotTests: needs bake time after migration from continue-on-error workflow job

[radical]

Context

RustPolyglotTests.CreateRustAppHostWithRedisIntegration was migrated from the legacy polyglot-validation.yml workflow's Rust SDK Validation job in PR #16965. The legacy job ran with continue-on-error: true as a paranoid safety net.

The migrated C# test runs the same scenario (scaffold a Rust AppHost, add Aspire.Hosting.Redis, replace src/main.rs, run the AppHost, verify a Redis container materialized via the host Docker socket) but currently builds the AppHost from source inside Docker, which takes ~5 min of cargo build per run.

Action

Quarantine RustPolyglotTests for now so it does not gate PRs while we observe its stability on the post-migration code path. Unquarantine once we have several green runs in a row in the Quarantined Tests workflow.

Related

• PR Convert polyglot SDK validation to C# unit tests (#16701) #16965 (migration)
• Original workflow: .github/workflows/polyglot-validation/test-rust.sh (deleted in Convert polyglot SDK validation to C# unit tests (#16701) #16965)

[joperezr]

🤖 Aspire triage pass — 2026-05-12 07:28 UTC

Area: area-engineering-systems, area-polyglot (both already partially present; suggesting area-polyglot addition since the test is Rust polyglot-specific)
Kind: flaky-test (quarantine request)
Repro: yes-minimal — the issue itself names the specific test RustPolyglotTests.CreateRustAppHostWithRedisIntegration and references migration PR #16965 and the deleted .github/workflows/polyglot-validation/test-rust.sh
Affected version(s): not user-facing (CI / test infra only)
Severity: S4 — test infra hygiene; the request is to quarantine a newly-migrated test that previously ran with continue-on-error: true. No user impact.

Urgency: ⚪ backlog — no milestone
Reason: Quarantine-only request for a CI test post-migration; not a shipping regression, no user-facing scenario, S4. Does not meet servicing or vNext bar. Recommend leaving unmilestoned (or Backlog) until the unquarantine criteria (several green Quarantined Tests workflow runs) is met.

Suggested owner(s): @sebastienros (score 3), backup @mitchdenny (score 3)
Evidence:

• @sebastienros merged Unify ATS withReference exports #15238 ("Unify ATS withReference exports") in area-polyglot (only recent PR in that area in the last 90d).
• @mitchdenny merged Remove test-scenarios infrastructure #14639 ("Remove test-scenarios infrastructure") in area-engineering-systems (last 90d; relevant to test infra migrations).
• Issue author @radical (who did the migration in Convert polyglot SDK validation to C# unit tests (#16701) #16965) is excluded per owner-suggestion rules.
• No .github/CODEOWNERS paths cited in the issue body to refine further.

Confidence: medium — area is clearly engineering-systems + polyglot, but quarantine-action issues are typically self-served by the author; owner suggestion is weakly evidenced (single-PR scores).
Needs human?: no — straightforward quarantine request; author can self-action via the test-management skill / /quarantine-test command.

Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.