dotnet / dotnet/aspnetcore

Quarantine RedirectionTest.RedirectEnhancedNonBlazorGetToExternal is flaky

Open
#68,947 0 comments 0 reactions 1 assignee Claimed by @BhaskarSuresh22 View on GitHub
area-blazor test-failure
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 10h
Merged PRs (30d)
281

Description

## Failing Test(s)
- `Microsoft.AspNetCore.Components.E2ETests.ServerRenderingTests.RedirectionTest.RedirectEnhancedNonBlazorGetToExternal`

## Details

This test has failed intermittently on `main` in the past 30 days with a WebDriver/browser-startup timeout signature (`OpenQA.Selenium.WebDriverException` → `TaskCanceledException`), the same signature that led to the related-but-distinct quarantine of `RedirectStreamingPostToExternal`/`RedirectEnhancedPostToExternal` in #68849:
- Build [1551326](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1551326&view=results) (2026-08-13)
- Build [1537561](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1537561&view=results) (2026-08-03)

The failures are separated by many passing runs, so this is browser/WebDriver flakiness rather than a consistent regression. The test has never previously carried a `[QuarantinedTest]` attribute.

Quarantined via #aw_redirext.

> Generated by [Daily Test Quarantine Management](https://github.com/dotnet/aspnetcore/actions/runs/33496438442) · auto · 240.4 AIC · ⌖ 10.9 AIC · ⊞ 4.3K · [◷](https://github.com/search?q=repo%3Adotnet%2Faspnetcore+is%3Aissue+%22gh-aw-workflow-call-id%3A+dotnet%2Faspnetcore%2Ftest-quarantine%22&type=issues)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.