Reactivate ActiveIssue tests in Microsoft.Extensions where the issue is no longer active

[svick]

There are 45 [ActiveIssue] attributes in Microsoft.Extensions tests that point to issues that are no longer active (i.e. the issues are closed). I think these tests should be reactivated, if possible. If removing some [ActiveIssue] is more complicated, we can create a dedicated issue for it (or ignore it for now).

Specifically:

Closed issue	Affected tests/scope
runtime#35970	Microsoft.Extensions.Caching.Memory.Tests — assembly-wide, limited to the Mono runtime
runtime#33894	ServiceProviderCompilationTest — class-wide, limited to the Mono runtime; CompilesInLimitedStackSpace is also separately marked for Mono
runtime#34091	10 tests in LoggerFactoryExtensionsTest and LoggerTest
runtime#37669, runtime#73432	XmlConfigurationTest.LoadKeyValuePairsFromValidEncryptedXml
runtime#42036	CanSetValuesAndReloadValues, CreatingOptionalFileInNonExistentDirectoryWillReload, DeletingFilesThatRedefineKeysWithReload, DeletingFileWillReload, CreatingWritingDeletingCreatingFileWillReload
runtime#43411	DI.External.Tests — assembly-wide, limited to Browser
runtime#48696	HostTests.CreateDefaultBuilder_ConfigJsonDoesNotReload
runtime#50867	Three Configuration.Ini tests in IniConfigurationExtensionsTest and IniConfigurationTest
runtime#50872	ReadsRuntimeTargetInfoWithCommentsIsInvalid, RejectsMissingLibrary
runtime#50873	Six Http tests across DefaultHttpMessageHandlerBuilderTest, HttpMessageHandlerBuilderTest, and HttpClientFactoryServiceCollectionExtensionsTest
runtime#50875	Five Logging tests in LoggerFilterTest and LoggerMessageTest
runtime#50877	ConfigureOptionsThrowsWithAction, ConfigureOptionsThrowsIfNothingFound
runtime#52062	ConfigurationBindingGeneratorTests, LoggerMessageGeneratorEmitterTests, and LoggerMessageGeneratorParserTests — class-wide, limited to Browser
runtime#52319	FileConfigurationProviderTest.ProviderThrowsInvalidDataExceptionWhenLoadFails
roslyn#52527	LoggerMessageGeneratedCodeTests.MessageTests_SuppressWarning_WarnAsError_NoError

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

[svick]

Phase 1 is implemented in #132740. Most of the closed-issue skips listed here were removed and the resulting test set was exercised through five full CI runs plus the CoreCLR library outer-loop and extra-platform pipelines.

The following cases/scopes are not re-enabled in the final PR:

• Diagnostics from Source Generators do not respect suppression roslyn#52527 — LoggerMessageGeneratedCodeTests.MessageTests_SuppressWarning_WarnAsError_NoError

  • This was attempted locally before publishing the PR.
  • Enabling the test and its generator inputs caused the test project to fail compilation with 12 SYSLIB1015 diagnostics. The failure occurs before the test can run because the logging source-generator diagnostics still do not honor the /warnAsError plus /noWarn scenario expected by the test.
  • The ActiveIssue marker, disabled test body, and disabled M2–M4 generator inputs therefore remain in place.

• Microsoft.Extensions.Caching.Memory.Tests hanging in Mono after test execution finishes #35970 — Microsoft.Extensions.Caching.Memory.Tests assembly

  • The initial CI run exercised the assembly in Browser configurations after removing both the assembly-level skip and the related project exclusion.
  • Browser runs on Linux and Windows, using both Mono and CoreCLR, produced 19–25 failures per run. The failures covered many tests and included unsupported platform operations and assertion failures, rather than one isolated flaky test.
  • Because the reactivation exposed an assembly-wide unsupported scope, the complete original state was restored: the Mono assembly ActiveIssue, <IgnoreForCI> gate, and Browser project exclusion remain.
  • Detailed logs are recorded in the run-1 PR comment.

• Blazor client developers can use Parallel.For in their applications to share more code with server #43411 — Microsoft.Extensions.DependencyInjection.ExternalContainers.Tests assembly on Browser

  • Each Browser run produced 63 failures, primarily PlatformNotSupportedException: Operation is not supported on this platform.
  • This consistently affected the assembly across Mono and CoreCLR Browser configurations, so the assembly-wide Browser ActiveIssue remains.
  • Detailed logs are recorded in the run-1 PR comment.

• [wasm] Enable crypto and related tests  #37669 / Annotate System.Security.Cryptography.Xml for trimming #73432 — XmlConfigurationTest.LoadKeyValuePairsFromValidEncryptedXml on Browser and aggressive trimming

  • The reactivated test failed on Browser under both Mono and CoreCLR with PlatformNotSupportedException: Algorithm 'Aes' is not supported on this platform.
  • The test was restored to its original state, so both the Browser condition and the aggressive-trimming condition remain. The Browser failure was directly observed; aggressive trimming was not independently revalidated after reverting the failed test as a whole.
  • Detailed logs are recorded in the run-1 PR comment.

The five tests associated with #42036 were not changed by #132740 because they were already active on main; they are not among the cases left disabled.

After restoring the scopes above, none of the reactivations retained in the PR failed during the five full CI runs. Failures seen in later runs and optional pipelines were unrelated to these changes.

Note

This comment was generated with GitHub Copilot.