Emit IL for AsyncResumptionStub#121456
Merged
Merged
Build Analysis / Build Analysis
failed
Nov 14, 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.
Build Failures
runtime / Build / linux-arm Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/coreclr/tools/Common/TypeSystem/IL/Stubs/AsyncResumptionStub.cs(17,35): error CS0649: Field 'AsyncResumptionStub._owningType' is never assigned to, and will always have its default value null
runtime / Build / linux_musl-arm Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/coreclr/tools/Common/TypeSystem/IL/Stubs/AsyncResumptionStub.cs(17,35): error CS0649: Field 'AsyncResumptionStub._owningType' is never assigned to, and will always have its default value null
runtime / Build / linux_musl-arm64 Debug AllSubsets_CoreCLR_ReleaseRuntimeLibs / Build product
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌src/coreclr/tools/Common/TypeSystem/IL/Stubs/AsyncResumptionStub.cs(17,35): error CS0649: Field 'AsyncResumptionStub._owningType' is never assigned to, and will always have its default value null
51 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime] [dotnet-linker-tests] [runtime-dev-innerloop]
Was this helpful?
Loading