Skip to content

Fix reporting Hot Reload capabilities of WASM projects#53665

Merged
tmat merged 4 commits into
dotnet:release/10.0.3xxfrom
tmat:FixWasmCapabilityLogging
Apr 15, 2026
Merged

Fix reporting Hot Reload capabilities of WASM projects#53665
tmat merged 4 commits into
dotnet:release/10.0.3xxfrom
tmat:FixWasmCapabilityLogging

Merge branch 'release/10.0.3xx' into FixWasmCapabilityLogging

96cc911
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Apr 14, 2026 in 0s

.NET Result Analysis

Details

‼️ Build Analysis Check Result has been manually overridden

  • The build analysis check result has been updated by the user for the following reason: Unrelated test issues:

    All test failures in PR #53665 are already tracked:

    1. ✅ C++/CLI tests (8 failures) — Tracked by #53789 (#53789; — VS 2026 Helix
      machines missing v143 platform toolset
    • SourceLinkTests.Cpp
    • GivenThatWeWantToBuildACppCliProject.* (4 methods)
    • GivenThatWeWantToBuildACppCliProjectWithTransitiveDeps.* (3 methods)
    • GivenThatWeWantToPublishACppCliProject.When_referenced_by_csharp_project_it_publishes_and_runs
    1. ✅ It_publishes_the_project_with_a_refs_folder_and_correct_deps_file (net46) — Tracked by #53796
      (#53796; — mscorlib.dll vs .NETFramework/v4.6/m… string mismatch

  • The check result has changed from Failure to Success

Tip

To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.

Test Failures (15 tests failed)

🔹 [All failing tests from dotnet-sdk-public-ci]

Was this helpful? Yes No