Conversation
…rantine ShutdownTests.OutOfProcessToInProcessHostingModelSwitchWorks - Re-quarantine WebWorkerTemplateE2ETest at class level (was unquarantined in #66072, failing again in build 1373142) - Quarantine BlazorWasmTemplateTest at class level (NU1603 NuGet restore failures in builds 1342501 and 1373142) - Unquarantine ShutdownTests.OutOfProcessToInProcessHostingModelSwitchWorks (100% pass rate in quarantine pipeline for 30+ days) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Apr 13, 2026
Open
Member
|
CC @ilonatommy - we have some real new failures in the |
ilonatommy
approved these changes
Apr 13, 2026
src/ProjectTemplates/test/Templates.Blazor.Tests/WebWorkerTemplateE2ETest.cs
Outdated
Show resolved
Hide resolved
src/ProjectTemplates/test/Templates.Blazor.Tests/BlazorWasmTemplateTest.cs
Outdated
Show resolved
Hide resolved
ilonatommy
added a commit
to ilonatommy/aspnetcore
that referenced
this pull request
Apr 14, 2026
Remove quarantine attributes added in dotnet#66294 since the root cause (broken DevServer version pin) is fixed in the previous commit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ilonatommy
added a commit
to ilonatommy/aspnetcore
that referenced
this pull request
Apr 14, 2026
Remove quarantine attributes added in dotnet#66294 since the root cause (broken DevServer version pin) is fixed in the previous commit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ilonatommy
added a commit
that referenced
this pull request
Apr 14, 2026
* Fix DevServer version pin in template test infrastructure The version pin added in #65784 to prevent NU1603 errors during Blazor WASM template tests never worked because is not an MSBuild property available in the test build context. It is only computed dynamically during template packing by GenerateContent.targets. This caused the generated Directory.Build.targets to contain an empty condition ('' != '') and empty version range ([]), making the pin a no-op. When a darc feed contains a preview-versioned DevServer package that outranks the locally-built CI package in SemVer (e.g. 11.0.0-preview.1 > 11.0.0-ci), NuGet resolves to the feed version, triggering NU1603 which is fatal with TreatWarningsAsErrors. Fix: use which is always available in the build context and matches the DevServer package version since all aspnetcore packages share the same version. Fixes #66293 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Unquarantine BlazorWasmTemplateTest and WebWorkerTemplateE2ETest Remove quarantine attributes added in #66294 since the root cause (broken DevServer version pin) is fixed in the previous commit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR makes three test quarantine management changes:
1. Re-quarantine
WebWorkerTemplateE2ETest(class-level)Associated issue: #66292
These tests were unquarantined in #66072 on 2026-04-02 but are failing again. Build 1373142 (2026-04-10) shows all 4 methods failing with the same
NU1603NuGet restore error:Microsoft.AspNetCore.Components.WebAssembly.DevServer 11.0.0-ciwas not found on the Windows CI agent.2. Quarantine
BlazorWasmTemplateTest(class-level)Associated issue: #66293
All 3 tests in this class fail with the same
NU1603NuGet restore error, in builds 1342501 and 1373142. This is the same root cause as the WebWorker template tests (both use theblazorwasmtemplate).3. Unquarantine
ShutdownTests.OutOfProcessToInProcessHostingModelSwitchWorksThe test has been reliably passing for 30+ days (quarantined since 2024-06-05, issue #55937). All 4 variants (FunctionalTests, NewHandler.FunctionalTests, NewShim.FunctionalTests, IISExpress.FunctionalTests) show 100% pass rate (46/46 passes, 21/30 builds = 70%) in the quarantine pipeline (definition 84) over the last 30 days.
Note
🔒 Integrity filter blocked 5 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: