[ci-scan] profiler/runtimeasyncapis test fails (PROFILER TEST FAILED) on R2R_CG2 crossgen2 runs #132917

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1569780
Build error leg or test failing: coreclr Pri0 Runtime Tests Run R2R_CG2 (profiler work item) - profiler/runtimeasyncapis/runtimeasyncapis

Error Details

The profiler/runtimeasyncapis/runtimeasyncapis test fails on the crossgen2 (def 124) R2R_CG2 profiler work item across multiple OS/arch legs (linux, osx, windows; x64 and arm64). The RuntimeAsyncApisProfiler does not print the expected PROFILER TEST PASSES marker from its Shutdown() method, so the harness reports the profilee returned exit code 100 and fails, then the process aborts (createdump, exit 134). The failure reproduces across def-124 builds 1567889 and 1569780 (~39 failed work items per build), so it blocks clean CI.

07:20:01.517 Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
Profilee STDOUT: RuntimeAsyncApisProfiler: failures=0 jit=0/0 ip=0 il=0 thrown=2 searches=0 unwinds=0 catchers=2
Profilee STDOUT: PROFILER TEST FAILED
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 100.
Expected: 100
Actual: 134
END EXECUTION - FAILED

Error Message

{
  "ErrorMessage": "Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

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 · 1K AIC · ⌖ 13.5 AIC · ⊞ 20.7K · ◷

Report

Summary