Tracking a known CI failure on the runtime-diagnostics pipeline. No code action required: the failure will resolve itself once Microsoft.AspNetCore.App is rebuilt against a runtime that includes #127889 and flows back via the next dotnet/dotnet Maestro update. The pinned ASP.NET shared framework currently used by the WebApp3 debuggee was R2R-compiled against the pre-#127889 runtime, so its baked-in call sites reference the old AsyncHelpers.CaptureContexts signature; once ASP.NET rebuilds against the new runtime the R2R images will reference the new 3-arg signature and the test will pass again.
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1435092
Build error leg or test failing: runtime-diagnostics -> DAC_x64 / cDAC_x64 / cDAC_no_fallback_x64 -> SOSScenarioTests.WebApp3
Pull request: N/A (rolling)
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "MissingMethodException: Method not found: 'Void System.Runtime.CompilerServices.AsyncHelpers.CaptureContexts",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Root cause
PR #127889 changed AsyncHelpers.CaptureContexts from a 2-arg to a 3-arg signature. R2R-compiled assemblies in the pinned Microsoft.AspNetCore.App shared framework still bake call sites to the old 2-arg helper. Loading those R2R images against the new runtime throws MissingMethodException from GenericWebHostService.StartAsync at WebApp3 startup, which leaves an empty dump file that CDB then fails to open with NTSTATUS 0xC000011E -- the misleading surface error the test reports.
Bisect (cDAC_x64_release WebApp3): last pass 7da2acb927da (5/24), first fail 17cd11cc909c (5/25); only d198593b056 (#127889) is non-docs in that window.
Report
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 0 |
0 |
0 |
Tracking a known CI failure on the
runtime-diagnosticspipeline. No code action required: the failure will resolve itself onceMicrosoft.AspNetCore.Appis rebuilt against a runtime that includes #127889 and flows back via the nextdotnet/dotnetMaestro update. The pinned ASP.NET shared framework currently used by the WebApp3 debuggee was R2R-compiled against the pre-#127889 runtime, so its baked-in call sites reference the oldAsyncHelpers.CaptureContextssignature; once ASP.NET rebuilds against the new runtime the R2R images will reference the new 3-arg signature and the test will pass again.Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1435092
Build error leg or test failing:
runtime-diagnostics-> DAC_x64 / cDAC_x64 / cDAC_no_fallback_x64 ->SOSScenarioTests.WebApp3Pull request: N/A (rolling)
Error Message
Fill the error message using step by step known issues guidance.
{ "ErrorMessage": "MissingMethodException: Method not found: 'Void System.Runtime.CompilerServices.AsyncHelpers.CaptureContexts", "BuildRetry": false, "ExcludeConsoleLog": false }Root cause
PR #127889 changed
AsyncHelpers.CaptureContextsfrom a 2-arg to a 3-arg signature. R2R-compiled assemblies in the pinnedMicrosoft.AspNetCore.Appshared framework still bake call sites to the old 2-arg helper. Loading those R2R images against the new runtime throwsMissingMethodExceptionfromGenericWebHostService.StartAsyncat WebApp3 startup, which leaves an empty dump file that CDB then fails to open withNTSTATUS 0xC000011E-- the misleading surface error the test reports.Bisect (cDAC_x64_release WebApp3): last pass
7da2acb927da(5/24), first fail17cd11cc909c(5/25); onlyd198593b056(#127889) is non-docs in that window.Report
Summary