Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1571879
Build error leg or test failing: R2R_Composite linux x64 checked (azurelinux.3.amd64.open.rt) — profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
Pipeline: runtime-coreclr crossgen2 outerloop (definition 134), branch main. The runtimeasyncapis profiler test fails on the crossgen2 R2R legs: the profilee app returns exit code 100 and its console output never contains PROFILER TEST PASSES, so Profiler.Tests.ProfilerTestRunner fails the test with System.Exception. The failure spans the R2R profiler work items (35 failed work items in source build 1571879) and reproduces in follow-up build 1573564.
KBE authoring guidance (ci-failure-scan)
Error Details is for readers. Paste the full exception so the failure is understandable without opening the raw log.- Build Analysis parses only the single JSON block under
Error Message.
ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
Error Details
Running test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
Unhandled exception. System.Exception: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test. Usually it is printed from the Shutdown() method of the profiler implementation. This text was not found in the output above. Profilee returned exit code 100.
at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
at Profiler.Tests.ProfilerTestRunner.Run(...)
at RuntimeAsyncApis.Main(String[] args)
Profilee STDOUT: PROFILER TEST FAILED
END EXECUTION - FAILED
Error Message
{
"ErrorMessage": [
"runtimeasyncapis.cmd",
"Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app",
"Profilee returned exit code 100."
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 2 hits in failure.log
First build it occurred
Source build 1571879 (2026-08-28); reproduces in follow-up build 1573564 (2026-08-29), where 35 R2R profiler work items failed with this signature.
Duplicate search
Searched open/closed issues and PRs for runtimeasyncapis, PROFILER TEST PASSES, and ProfilerTestRunner in the crossgen2 R2R context. Existing runtime-async profiler issues (e.g. #132311) are browser/wasm-specific AsyncProfilerTests FailFast crashes, a different leg and signature. No open Known Build Error matches this crossgen2 R2R runtimeasyncapis exit-100 failure.
Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments to loop in owners — it never disables the test.
Generated by CI Outer-Loop Failure Scanner · opus48 · 951 AIC · ⌖ 16 AIC · ⊞ 20.7K · ◷
Report
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 6 |
26 |
26 |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1571879
Build error leg or test failing: R2R_Composite linux x64 checked (azurelinux.3.amd64.open.rt) — profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
Pipeline:
runtime-coreclr crossgen2 outerloop(definition 134), branchmain. Theruntimeasyncapisprofiler test fails on the crossgen2 R2R legs: the profilee app returns exit code 100 and its console output never containsPROFILER TEST PASSES, soProfiler.Tests.ProfilerTestRunnerfails the test withSystem.Exception. The failure spans the R2Rprofilerwork items (35 failed work items in source build 1571879) and reproduces in follow-up build 1573564.KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception so the failure is understandable without opening the raw log.Error Message.ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.Error Details
Error Message
{ "ErrorMessage": [ "runtimeasyncapis.cmd", "Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app", "Profilee returned exit code 100." ], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 2 hits in failure.log
First build it occurred
Source build 1571879 (2026-08-28); reproduces in follow-up build 1573564 (2026-08-29), where 35 R2R
profilerwork items failed with this signature.Duplicate search
Searched open/closed issues and PRs for
runtimeasyncapis,PROFILER TEST PASSES, andProfilerTestRunnerin the crossgen2 R2R context. Existing runtime-async profiler issues (e.g. #132311) are browser/wasm-specificAsyncProfilerTestsFailFast crashes, a different leg and signature. No openKnown Build Errormatches this crossgen2 R2Rruntimeasyncapisexit-100 failure.Filed by
ci-failure-scan(detection only).ci-failure-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments to loop in owners — it never disables the test.Report
Summary