builds breaking because analyzers fail with `Value cannot be null. (Parameter 'type')`

[radical]

Failing rolling build hit for browser-wasm windows Release LibraryTests_AOT:

CSC : error CS8032: An instance of analyzer Microsoft.NetCore.CSharp.Analyzers.Resources.CSharpMarkAssembliesWithNeutralResourcesLanguageAnalyzer cannot be created from D:\a\_work\1\s\.packages\microsoft.codeanalysis.netanalyzers\8.0.0-preview1.23117.2\analyzers\dotnet\cs\Microsoft.CodeAnalysis.CSharp.NetAnalyzers.dll : Value cannot be null. (Parameter 'type'). [D:\a\_work\1\s\src\libraries\System.ComponentModel.Composition.Registration\src\System.ComponentModel.Composition.Registration.csproj::TargetFramework=net8.0]

Changes since the last passing rolling build - f6bed51...2819a94

cc @lewing @steveisok

Known Issue Error Message

Fill the error message using known issues guidance.

{
  "ErrorPattern": ".*An instance of analyzer Microsoft.NetCore.CSharp.Analyzers.Resources.CSharpMarkAssembliesWithNeutralResourcesLanguageAnalyzer cannot be created .*Value cannot be null.*",
  "BuildRetry": false
}

Report

Build	Definition	Step Name	Console log	Pull Request
180513	dotnet/runtime	Restore and Build Product	Log	#82476
180257	dotnet/runtime	Restore and Build Product	Log	#82350
179712	dotnet/runtime	Build product	Log

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	3	3

[lewing]

This isn't specific to wasm is it?

[lewing]

https://dev.azure.com/dnceng-public/public/_build/results?buildId=180566&view=logs&j=f3b7e53d-5a04-5317-3e8c-82ae7488ad7d&t=b32ae8c0-c4d6-5d0a-6327-bd5df8cb1d69&l=1376

not mono or wasm specific

[lewing]

cc @pavelsavara @RikkiGibson @jkoritzinsky

[stephentoub]

Seems pretty much every PR is hitting this on at least one leg. It's also not always the same analyzer failing.

Did we recently take updates to anything to do with Roslyn, compiler dependencies, etc?

[jkoritzinsky]

Yes, we recently updated Roslyn. We have a PR out to revert the update as it's also causing timeouts.

[stephentoub]

cc: @jaredpar