Introduce a new internal EventSourceGenerator and use it for all ES implementations#121180
Merged
Build Analysis / Build Analysis
failed
Nov 9, 2025 in 0s
.NET Result Analysis
Details
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.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known Repository Errors
Build Failures
runtime / Build / linux-arm Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.Diagnostics.DiagnosticSource/src/System/Diagnostics/DiagnosticSourceEventSource.cs(162,1): error CS1022: Type or namespace definition, or end-of-file expected
runtime / Build / linux_musl-arm Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/libraries/System.Diagnostics.DiagnosticSource/src/System/Diagnostics/DiagnosticSourceEventSource.cs(162,1): error CS1022: Type or namespace definition, or end-of-file expected
runtime / Build / windows-arm64 Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src\libraries\System.Diagnostics.DiagnosticSource\src\System\Diagnostics\DiagnosticSourceEventSource.cs(162,1): error CS1022: Type or namespace definition, or end-of-file expected
88 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime] [runtime-dev-innerloop] [dotnet-linker-tests]
Was this helpful?
Loading