Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1583047
Build error leg or test failing: coreclr Pri1 Runtime Tests Run linux x64/arm64 & osx arm64 checked (interpreter) - profiler work item - profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
On the runtime-interpreter pipeline, the profiler runtime-test work item consistently fails on runtimeasyncapis. The profilee (run with DOTNET_RuntimeAsync=1, DOTNET_ENABLE_PROFILING=1) aborts with exit code 134 and never prints PROFILER TEST PASSES, so the out-of-process test asserts (expected 100, actual 134). Reproduced in consecutive builds on main (1583047, 1585871) across linux-x64, linux-arm64, and osx-arm64 legs.
KBE authoring guidance (ci-failure-scan)
Error Details is for readers. Paste the full exception, stack trace, or build error excerpt 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.
- Set
BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.
Error Details
Profilee STDOUT: Profiler.dll!DllGetClassObject
Profilee STDOUT: Profiler.dll!Profiler::Initialize
Test failed: 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 134.
Expected: 100
Actual: 134
END EXECUTION - FAILED
Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
Error Message
{
"ErrorMessage": [
"Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd",
"Profiler tests are expected to contain the text 'PROFILER TEST PASSES'"
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log
Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.
Generated by CI Outer-Loop Failure Scanner · opus48 · 994 AIC · ⌖ 17.9 AIC · ⊞ 19.5K · ◷
Report
Summary
| 24-Hour Hit Count |
7-Day Hit Count |
1-Month Count |
| 0 |
0 |
0 |
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1583047
Build error leg or test failing:
coreclr Pri1 Runtime Tests Run linux x64/arm64 & osx arm64 checked(interpreter) -profilerwork item -profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmdOn the
runtime-interpreterpipeline, theprofilerruntime-test work item consistently fails onruntimeasyncapis. The profilee (run withDOTNET_RuntimeAsync=1,DOTNET_ENABLE_PROFILING=1) aborts with exit code 134 and never printsPROFILER TEST PASSES, so the out-of-process test asserts (expected 100, actual 134). Reproduced in consecutive builds onmain(1583047, 1585871) across linux-x64, linux-arm64, and osx-arm64 legs.KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorMessageis a case-sensitive ordinalString.Containssubstring copied verbatim from the failing log.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
Error Message
{ "ErrorMessage": [ "Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd", "Profiler tests are expected to contain the text 'PROFILER TEST PASSES'" ], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log
Filed by
ci-failure-scan(detection only).ci-failure-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.Report
Summary