Quarantine RedirectionTest.RedirectStreamingEnhancedPostToExternal

[DeagleGross]

Failing Test(s)

Microsoft.AspNetCore.Components.E2ETests.ServerRenderingTests.RedirectionTest.RedirectStreamingEnhancedPostToExternal

Error Message

(Error message not available via test results API — this is a browser E2E test)

Stacktrace

Details

(Not available — E2E browser automation test)

Logs

Details

The test clicks a form submit button and expects the browser to navigate to microsoft.com via a streaming enhanced POST to an external URL. This test is flaky in the components-e2e pipeline (pipeline 87), likely due to external network timing, browser automation variability, or race conditions in enhanced navigation handling.

The related test RedirectStreamingEnhancedGetToInternal is already quarantined via issue #66709.

Build

• https://dev.azure.com/dnceng-public/public/_build/results?buildId=1436713&view=results
• https://dev.azure.com/dnceng-public/public/_build/results?buildId=1405887&view=results

Generated by Daily Test Quarantine Management · sonnet46 11.7M · ◷

[DeagleGross]

Investigation

The test RedirectStreamingEnhancedPostToExternal is a Blazor E2E browser automation test that:

1. Clicks a form submit button to trigger an enhanced POST request
2. Expects the browser to navigate to microsoft.com after a streaming redirect to an external URL

Failures observed: 2 times across builds 1436713 and 1405887 in pipeline 87 (components-e2e).

Root cause: The test likely fails due to:

• External network timeouts when navigating to microsoft.com
• Race conditions in Blazor's enhanced navigation POST handling
• Browser automation timing issues

The sibling test RedirectStreamingEnhancedGetToInternal is already quarantined via #66709 with similar symptoms, suggesting this class of streaming redirect E2E tests is prone to flakiness.

No obvious code fix is identifiable without deeper reproduction of the failure. Quarantining until the underlying flakiness is resolved.

Generated by Daily Test Quarantine Management · sonnet46 11.7M · ◷

[DeagleGross]

Triage Summary

Area: area-blazor — The failing test is Microsoft.AspNetCore.Components.E2ETests.ServerRenderingTests.RedirectionTest.RedirectStreamingEnhancedPostToExternal, which is a Blazor E2E browser automation test for streaming enhanced navigation/redirect behavior in the Components pipeline.

Type: Bug — A flaky test that consistently fails in the components-e2e pipeline (pipeline 87) across multiple builds, indicating an intermittent but real issue.

Potential Duplicates

• [test-quarantine] Quarantine RedirectionTest.RedirectStreamingEnhancedPostToExternal #541 - [test-quarantine] Quarantine RedirectionTest.RedirectStreamingEnhancedPostToExternal (similarity: high — this is the associated PR/issue created by the same workflow run for the same test)
• The issue body references issue Quarantine RedirectionTest.RedirectStreamingEnhancedGetToInternal dotnet/aspnetcore#66709 (upstream repo) for the sibling test RedirectStreamingEnhancedGetToInternal, which was already quarantined for a similar reason.

Notes

• The issue already has the test-failure label applied.
• The flakiness is attributed to external network timing (navigating to microsoft.com), browser automation variability, or race conditions in enhanced navigation handling.
• A related quarantine PR was created (see [test-quarantine] Quarantine RedirectionTest.RedirectStreamingEnhancedPostToExternal #541) but the git push failed; the bundle artifact is available for manual PR creation.

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #540 · sonnet46 694.8K · ◷