You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CI Failure] Flaky: AzureKubernetesInfrastructureTests DestroyPipeline tests time out on windows-latest #19982
Build: https://github.com/microsoft/aspire/actions/runs/34240101007
Build error leg or test failing: Tests / No-package tests (regular, Aspire.Hosting.JavaScript.Tests, ...) / Hosting.JavaScript (windows-latest) / Aspire.Hosting.Azure.Tests.AzureKubernetesInfrastructureTests.DestroyPipelineUsesPersistedAksResourceIdWhenScopeIsAbsent
Pull request: #19386
Error Message
System.TimeoutException : The operation has timed out. at Aspire.Hosting.Azure.Tests.AzureKubernetesInfrastructureTests.DestroyPipelineUsesPersistedAksResourceIdWhenScopeIsAbsent()/DestroyPipelineUsesPersistedAksOutputAndScopeWithoutProvisioning() in AzureKubernetesInfrastructureTests.cs
Description
Flaky: AzureKubernetesInfrastructureTests DestroyPipeline tests time out on windows-latest
Closure recommendation: no recurrence in 7 days of CI
Window: ci.yml attempt-1 runs from 2026-10-25T10:57Z to 2026-11-01T09:51Z (824 runs). I grepped every failed test-job log in that window (968 of 968 downloaded).
Tests: the AzureKubernetesInfrastructureTests.DestroyPipeline* methods, which are still present on main (1bccada).
Aspire.Hosting.Azure.Kubernetes.Tests lane jobs: main 63 Linux / 63 Windows, PR 218 Linux / 218 Windows.
Failures: 0. No DestroyPipeline test appears in any failed job log, in any lane.
Last recorded occurrence: 2026-09-10, run 34480468710.
Fixing PR: none identified.
I recommend closing this. Reopen it if the signature comes back.
Activity
radical commentedon Sep 8, 2026
[automated] The CI shepherd is watching this failure.
Current assessment: Watch this same-day-test-recurrence for a cross-day failure or positive recovery.
Evidence reviewed:
Evidence still needed:
Reassess when: After an independent failure on a different day or positive recovery.
No quarantine, retry, closure, or investigation has been started.
davidfowl commentedon Nov 1, 2026
Closure recommendation: no recurrence in 7 days of CI
AzureKubernetesInfrastructureTests.DestroyPipeline*methods, which are still present on main (1bccada).DestroyPipelinetest appears in any failed job log, in any lane.I recommend closing this. Reopen it if the signature comes back.
🤖 Posted by AspireAgent (AI Agent)