[ci-scan] Test failure: profiler/gc/nongcheap/nongcheap.cmd fails with missing 'PROFILER TEST PASSES'

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1523377
Build error leg or test failing: gc-standalone (def 146) Windows-x64 - profiler/gc/nongcheap/nongcheap.cmd
First build it occurred: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1523377
Also observed in follow-up build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1527159

Error Details

Running test: profiler/gc/nongcheap/nongcheap.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)
Failed test: profiler/gc/nongcheap/nongcheap.cmd

Error Message

{
  "ErrorMessage": [
    "Running test: profiler/gc/nongcheap/nongcheap.cmd",
    "Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test."
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

This Known Build Error was filed by the ci-failure-scan workflow; mitigation is handled separately by ci-failure-fix.

Note

This issue was generated by the GitHub Copilot-powered ci-failure-scan agentic workflow.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by CI Outer-Loop Failure Scanner · 818.7 AIC · ⌖ 11.7 AIC · ⊞ 18.6K · ◷

Report

Build	Repository	Test	Pull Request
1536423	dotnet/runtime	profiler/gc/nongcheap/nongcheap.cmd
1535992	dotnet/runtime	profiler/rejit/rejit/rejit.cmd	#131681
1535134	dotnet/runtime	profiler/elt/slowpatheltenter/slowpatheltenter.cmd	#131552
1533533	dotnet/runtime	profiler/ijw/ijw/ijw.cmd	#131578
1534185	dotnet/runtime	profiler.WorkItemExecution	#131510
1534188	dotnet/runtime	profiler/multiple/multiple/multiple.cmd	#131509
1534174	dotnet/runtime	profiler/dynamicoptimization/DynamicOptimization/DynamicOptimization.cmd	#131508
1533113	dotnet/runtime	profiler/gcheapenumeration/gcheapenumeration/gcheapenumeration.cmd
1532956	dotnet/runtime	profiler/ijw/ijw/ijw.cmd	#131578
1529665	dotnet/runtime	profiler/gcheapenumeration/gcheapenumeration/gcheapenumeration.cmd

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
1	10	10

[dotnet-policy-service]

Tagging subscribers to this area: @anicka-net, @dotnet/gc
See info in area-owners.md if you want to be subscribed.

[github-actions]

Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #131449

Note

AI/Copilot-generated triage note.

This Known Build Error has no producible automated code change (reason: standalone-GC / profiler runtime interaction — a native runtime code path that must not be auto-patched), so I could not open even a best-effort PR. Looping in owners so it can be fixed forward rather than muted.

Root cause (best analysis)

profiler/gc/nongcheap/nongcheap.cmd fails on the gc-standalone (def 146) Windows-x64 leg. The profilee exits 100 but never prints PROFILER TEST PASSES:

System.Exception: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' ...
This text was not found in the output above. Profilee returned exit code 100.

The PROFILER TEST PASSES string is emitted from the profiler's Shutdown() after it validates non-GC-heap object callbacks. Under the standalone GC, the non-GC-heap (frozen/immortal) object reporting the profiler relies on differs from the built-in GC, so the profiler's expected callbacks are not satisfied and it never reaches the passing print. This is a standalone-GC vs. profiler-nongcheap-enumeration interaction in native runtime/GC code (compare with the closely related gcstandalone profiler KBEs #128080 and #129962).

Evidence

• Failing build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1523377
• Also observed: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1527159
• First build it occurred: build 1523377 (per KBE); may not be the true origin.
• Possible related PR: none identified with sufficient confidence.

Suggested reviewers / area contacts

• Likely author: none identified with sufficient confidence.
• Area owners (area-GC-coreclr): @anicka-net, @dotnet/gc

A fix would likely involve ensuring the standalone GC reports non-GC-heap objects to the profiling API consistently with the built-in GC, so the profiler's nongcheap enumeration callbacks fire.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by CI Outer-Loop Failure Fixer · 396.3 AIC · ⌖ 17.9 AIC · ⊞ 17.1K · ◷