Skip to content

Quarantine BlazorWasmTemplateTest (NU1603 NuGet restore failures) #66293

Description

@github-actions

Failing Test(s)

BlazorTemplates.Tests.BlazorWasmTemplateTest.BlazorWasmStandaloneTemplate_Works
BlazorTemplates.Tests.BlazorWasmTemplateTest.BlazorWasmStandalonePwaTemplate_Works
BlazorTemplates.Tests.BlazorWasmTemplateTest.BlazorWasmStandaloneTemplate_AzureActiveDirectoryTemplate_Works

Error Message

Project new blazorwasm  --no-restore failed to restore. Exit code 1.
error NU1603: Warning As Error: AspNet.gyefbna1ouaa depends on Microsoft.AspNetCore.Components.WebAssembly.DevServer (>= 11.0.0-ci) but Microsoft.AspNetCore.Components.WebAssembly.DevServer 11.0.0-ci was not found. Microsoft.AspNetCore.Components.WebAssembly.DevServer 11.0.0-preview.1.26065.113 was resolved instead.
  Failed to restore ... (in 501 ms).

Stacktrace

Stack Trace
   at Templates.Test.Helpers.Project.RunDotNetNewAsync(String templateName, ...) in /_/src/ProjectTemplates/Shared/Project.cs:line 156
   at BlazorTemplates.Tests.BlazorTemplateTest.CreateBuildPublishAsync(...) in /_/src/ProjectTemplates/test/Templates.Blazor.Tests/BlazorTemplateTest.cs:line 42
   at BlazorTemplates.Tests.BlazorWasmTemplateTest.BlazorWasmStandaloneTemplate_Works(BrowserKind browserKind) in /_/src/ProjectTemplates/test/Templates.Blazor.Tests/BlazorWasmTemplateTest.cs:line 25

Logs

Console log
BlazorWasmStandaloneTemplate_Works(browserKind: Chromium) - Failed
BlazorWasmStandalonePwaTemplate_Works(browserKind: Chromium) - Failed
BlazorWasmStandaloneTemplate_AzureActiveDirectoryTemplate_Works - Failed

All tests fail with NU1603: Microsoft.AspNetCore.Components.WebAssembly.DevServer 11.0.0-ci was not found.
Microsoft.AspNetCore.Components.WebAssembly.DevServer 11.0.0-preview.1.26065.113 was resolved instead.

Build

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

Also failed in build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1342501

Note

🔒 Integrity filter blocked 5 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #65815 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #65817 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #65827 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #65816 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #65419 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Daily Test Quarantine Management · ● 9.9M · ◷

Activity

  1. self-assigned this
    on Apr 13, 2026
  2. added 2 commits that reference this issue on Apr 14, 2026
    eafe6c0
    a1f45a0
  3. added a commit that references this issue on Apr 14, 2026
    07e95ae
  4. github-actions commented on Apr 21, 2026

    @github-actions
    ContributorAuthor

    Re-quarantine: Tests Failing Again After Unquarantine

    The BlazorWasmTemplateTest tests were unquarantined in #66303 (2026-04-14) as part of a DevServer version pin fix. However, all 3 test methods are failing again in build 1388488 (2026-04-21).

    Failing Tests

    • BlazorWasmTemplateTest.BlazorWasmStandaloneTemplate_Works
    • BlazorWasmTemplateTest.BlazorWasmStandalonePwaTemplate_Works
    • BlazorWasmTemplateTest.BlazorWasmStandaloneTemplate_AzureActiveDirectoryTemplate_Works

    Analysis

    The failure pattern is identical to the previous failure: all 3 tests fail together in the same build. The same build also shows WebWorkerTemplateE2ETest and BlazorWebTemplateTest.BlazorWebTemplate_Works failures, which strongly suggests a common template test infrastructure root cause (possibly the same NU1603 NuGet DevServer version resolution issue that was thought to be fixed in #66303).

    The DevServer version pin fix may not have been fully effective, or a new preview package version in the NuGet feed has re-introduced the same conditions. The tests are being re-quarantined at the class level to stop CI breakage while the root cause is investigated.

    Re-quarantine PR: to be linked once merged.

    Generated by Daily Test Quarantine Management · ● 6.7M · ◷

  5. ilonatommy commented on Oct 26, 2026

    @ilonatommy
    Member

    @wtgodbe it got not reopened when the bot posted #66293 (comment) so we missed that it's not fixed. Is the bot already reopening on re-quarantine?

  6. added this to the .NET 12 Planning milestone on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions