Re-enable Blazor AppsettingsTests disabled during .NET 11 transition#124217
Merged
Re-enable Blazor AppsettingsTests disabled during .NET 11 transition#124217
Conversation
Co-authored-by: maraf <[email protected]>
github-actions
bot
added
the
needs-area-label
Copilot
AI
changed the title
[WIP] Re-enable tests from runtime issue 122338
Re-enable Blazor AppsettingsTests disabled during .NET 11 transition
Feb 10, 2026
maraf
added
arch-wasm
maraf
approved these changes
Feb 10, 2026
Contributor
|
Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR re-enables the Wasm.Build.Tests.Blazor.AppsettingsTests.FileInVfs test that was disabled during the .NET 10→11 transition. The test was failing due to runtime pack version mismatches (expected 11.0.0 but found 10.0.0). Now that the repository has completed the transition to .NET 11, the underlying issue is resolved and the test can be safely re-enabled.
Changes:
- Removed
[ActiveIssue]attribute blocking test execution - Added test class to CI execution list for automated testing on Helix
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/mono/wasm/Wasm.Build.Tests/Blazor/AppsettingsTests.cs | Removed [ActiveIssue] attribute from FileInVfs test method to re-enable execution |
| eng/testing/scenarios/BuildWasmAppsJobsList.txt | Added Wasm.Build.Tests.Blazor.AppsettingsTests to enable parallel test execution on Helix CI infrastructure |
ilonatommy
approved these changes
Feb 11, 2026
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.
Fixes #122338
Description
Wasm.Build.Tests.Blazor.AppsettingsTests.FileInVfswas disabled during the .NET 10→11 transition due to runtime pack path version mismatches. The repository is now on .NET 11.0.0, resolving the underlying issue.Changes
[ActiveIssue]attribute fromAppsettingsTests.FileInVfsWasm.Build.Tests.Blazor.AppsettingsTeststoBuildWasmAppsJobsList.txtfor CI executionTesting
Test logic unchanged. Original failure was environmental (version 10.0.0 vs expected 11.0.0), now resolved.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
aka.ms/usr/bin/curl curl -I -sSL --retry 5 --retry-delay 2 --connect-timeout 15 REDACTED o/mini/.. /home/REDACTED/work/runtime/runtime/src/mono/brows-fignore-exceptions ttin�� -DDISABLE_CONTRACTS(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.