System.Threading.Tasks.Tests.AsyncProfilerTests.StateMachineAsync_CallstackStressWithVaryingDepths [FAIL]
Expected at least 3 buffer flushes, got 2
----- BEGIN ASYNC EVENTS (CSV) -----
seq,delta,thread,event,disp,parent,frames,unwind
0,0,5056,AsyncProfilerMetadata,0,0,0,0
1,281,5056,ResetAsyncThreadContext,0,0,0,0
2,283,5056,CreateStateMachineAsyncContext,387,0,0,0
...
at AsyncProfilerTests.AssertTrue(EventDump dump, Boolean condition, String message)
at AsyncProfilerTests.StateMachineAsync_CallstackStressWithVaryingDepths()
No existing KBE matches this signature.
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1484168
Build error leg or test failing: windows-x64 Release - System.Threading.Tasks.Tests
Error Details
AsyncProfilerTests.StateMachineAsync_CallstackStressWithVaryingDepthsfails under jitstress mode in theruntime-coreclr libraries-jitstresspipeline (def 138). The test expects the async profiler to emit at least 3 buffer flushes, but only 2 are observed under stress conditions.Error Message
{ "ErrorMessage": ["StateMachineAsync_CallstackStressWithVaryingDepths", "Expected at least 3 buffer flushes"], "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Impact on platforms
First build it occurred
Duplicate search
"StateMachineAsync_CallstackStressWithVaryingDepths" label:"Known Build Error"— 0 results"StateMachineAsync_CallstackStressWithVaryingDepths" is:open— 0 results"CallstackStress" OR "buffer flushes" label:"Known Build Error" is:closed closed:>=2026-05-28— 0 results"StateMachineAsync_CallstackStressWithVaryingDepths" is:pr is:merged merged:>=2026-06-20— 0 resultsNo existing KBE matches this signature.
Related: #129920 (different AsyncProfilerTests failure on runtime-libraries-interpreter)
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.Note
🔒 Integrity filter blocked 4 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Report
Summary