Quarantine WebWorkerTemplateE2ETest (CanDisposeWorker, HandlesErrors, CanInvokeMethods, CanInvokeMethodsAfterPublish)

[wtgodbe]

Failing Test(s)

BlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_CanDisposeWorker
BlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_HandlesErrors
BlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_CanInvokeMethods
BlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_CanInvokeMethodsAfterPublish

Error Message

Detailed error messages unavailable from AzDO test results API and Helix logs. Tests consistently fail on both Linux and Windows CI agents. All four WebWorker template E2E tests fail across multiple test runs (isReRun: true).

Stacktrace

Stack trace

Stack traces unavailable from test results API. These are Selenium-based E2E template tests that run outside of Helix. The tests use Chromium browser automation to validate WebWorker template functionality.

Logs

Console log

WebWorkerTemplate_CanDisposeWorker(browserKind: Chromium) - Failed [80833 ms]
WebWorkerTemplate_HandlesErrors(browserKind: Chromium) - Failed [29347 ms]
WebWorkerTemplate_CanInvokeMethodsAfterPublish(browserKind: Chromium) - Failed [44587 ms]
WebWorkerTemplate_CanInvokeMethods(browserKind: Chromium) - Failed [28953 ms]

Tests failed on both Linux (run 37831318) and Windows (run 37841600) agents.

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1353846

[wtgodbe]

All four WebWorker template E2E tests are consistently failing on both Linux and Windows CI agents. The tests validate WebWorker template functionality (invoking methods, disposing workers, error handling, and post-publish invocation) using Selenium browser automation with Chromium. The high failure durations (29-80 seconds) suggest timeouts, which is typical of E2E template tests where the template project needs to be created, built, and run before browser automation can interact with it. The WebWorker feature is relatively new, and these tests may have infrastructure or template compatibility issues on CI agents. Unable to determine root cause without detailed error logs.

[github-actions]

Triage Summary

Area: area-blazor — Tests are in BlazorTemplates.Tests.WebWorkerTemplateE2ETest, covering Blazor WebWorker template E2E scenarios using Chromium/Selenium automation.
Type: test-failure — Already labeled; this is a CI test quarantine issue tracking consistently failing Selenium-based E2E tests on both Linux and Windows agents.

Potential Duplicates

• None found — No other open issues match this specific test class.

Notes

• All four WebWorkerTemplate* tests fail consistently (not flaky), with isReRun: true, suggesting a real breakage rather than intermittent flakiness.
• No stack traces are available from the test results API; investigation via AzDO build [1353846]((dev.azure.com/redacted) is recommended.
• The title says "Quarantine" — the fix would be either quarantining these tests or resolving the underlying failure.

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66035 · ◷