Skip to content

[ci-scan] Test failure: AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse on runtime-libraries-interpreter #129920

Closed
Closed
[ci-scan] Test failure: AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse on runtime-libraries-interpreter#129920
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsarea-Diagnostics-coreclrblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

Description

@github-actions
github-actions
bot
opened on Jun 27, 2026

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1479255
Build error leg or test failing: linux-x64 Release - System.Threading.Tasks.Tests

Error Details

AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse fails on the runtime-libraries-interpreter pipeline (def 330) on linux-x64. The test expects the async profiler to emit a RuntimeAsync_ConfigureAwaitFalse_Leaf_Marker event, but only RuntimeAsync_ConfigureAwaitFalse_Marker is present in the collection.

System.Threading.Tasks.Tests.AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse [FAIL]
      Assert.Contains() Failure: Item not found in collection
      Collection: ["RuntimeAsync_ConfigureAwaitFalse_Marker"]
      Not found:  "RuntimeAsync_ConfigureAwaitFalse_Leaf_Marker"
      ----- BEGIN ASYNC EVENTS (CSV) -----
      seq,delta,thread,event,disp,parent,frames,unwind
      0,0,9503,AsyncProfilerMetadata,0,0,0,0
      1,7600,9503,ResetAsyncThreadContext,0,0,0,0
      2,9800,9503,CreateRuntimeAsyncContext,733,731,0,0
      3,9801,9503,CreateRuntimeAsyncCallstack,733,731,1,0

Error Message

{
  "ErrorMessage": ["AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse", "RuntimeAsync_ConfigureAwaitFalse_Leaf_Marker"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Impact on platforms

  • runtime-libraries-interpreter (def 330) / linux-x64 Release / Helix queue: linux.x64
  • Also failing on osx-arm64 Release in the same pipeline

First build it occurred

Duplicate search

  • AsyncProfilerTests RuntimeAsync_ConfigureAwaitFalse label:"Known Build Error" — 0 results
  • RuntimeAsync_ConfigureAwaitFalse in:body — 0 results
  • AsyncProfilerTests ConfigureAwaitFalse is:open — 0 results
  • AsyncProfilerTests is:closed label:"Known Build Error" — 0 results

No existing KBE matches this signature.

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.

Note

🔒 Integrity filter blocked 10 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #129832 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #129876 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #82199 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #82139 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #82134 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • DiagnosticsTest Http2 SendAsync_Success_ConnectionSetupActivityGraphRecorded: Unexpected EOF trying to read request header #129771 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #108070 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #114229 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #112196 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #114222 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 51.1M · ◷

Report

Build Repository Test Pull Request
1485857 dotnet/runtime System.Threading.Tasks.Tests.AsyncProfilerTests.StateMachineAsync_CallstackStressWithVaryingDepths

Summary

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

Activity

  1. github-actions
    added
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    agentic-workflows
    on Jun 27, 2026
  2. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Jun 27, 2026
  3. jkotas
    added
    area-Diagnostics-coreclr
    on Jun 27, 2026

  4. jkotas commented on Jun 27, 2026

    @jkotas
    jkotas
    on Jun 27, 2026
    Member

    cc @lateralusX

  5. dotnet-policy-service commented on Jun 27, 2026

    @dotnet-policy-service
    dotnet-policy-servicebot
    on Jun 27, 2026 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to this area: @steveisok, @tommcdon, @dotnet/dotnet-diag
    See info in area-owners.md if you want to be subscribed.

  6. github-actions commented on Jun 28, 2026

    @github-actions
    github-actionsbot
    on Jun 28, 2026 – with GitHub Actions
    ContributorAuthor

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

    Note

    AI/Copilot-generated triage note.

    This Known Build Error has no producible automated code change (reason: the failure involves how the CoreCLR interpreter handles RuntimeAsync profiler event generation — an interpreter/runtime internal that exceeds automated fix bounds), 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)

    AsyncProfilerTests.RuntimeAsync_ConfigureAwaitFalse fails on the runtime-libraries-interpreter pipeline (linux-x64 and osx-arm64) because the async profiler callstack resolution does not capture all nested async frame names when running under the CoreCLR interpreter.

    The test calls a chain of three [RuntimeAsyncMethodGeneration(true)] methods:

    • RuntimeAsync_ConfigureAwaitFalse_Marker → _Mid_Marker → _Leaf_Marker

    It then expects all three method names to appear as frames in the deepest ResumeRuntimeAsyncCallstack event. Under the interpreter, only RuntimeAsync_ConfigureAwaitFalse_Marker appears:

    Assert.Contains() Failure: Item not found in collection
Collection: ["RuntimeAsync_ConfigureAwaitFalse_Marker"]
Not found:  "RuntimeAsync_ConfigureAwaitFalse_Leaf_Marker"

    The [RuntimeAsyncMethodGeneration(true)] attribute instructs the JIT to generate RuntimeAsync-aware code. The interpreter likely does not honor this attribute (or does not emit the corresponding profiler events for nested async frames), causing the leaf and mid method frames to be absent from the profiler callstack.

    The test precondition IsRuntimeAsyncSupported checks only !IsMonoRuntime (see PlatformDetection.cs:477), which returns true for the CoreCLR interpreter — so the test runs even though the interpreter may not fully support RuntimeAsync event generation.

    Evidence

    • Failing build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1479255
    • First failure: build 1464534 (2026-06-15T14:42:58Z)
    • Last success: build 1461427 (2026-06-12)
    • 6 consecutive failures through build 1482973 (2026-06-26)
    • Test source: src/libraries/System.Runtime/tests/System.Threading.Tasks.Tests/System.Runtime.CompilerServices/AsyncProfilerV2Tests.cs:1864
    • Platform detection: src/libraries/Common/tests/TestUtilities/System/PlatformDetection.cs:477 — IsRuntimeAsyncSupported => !IsMonoRuntime
    • Suspected regressing change: none identified — no changes to the test file, interpreter, or profiler code were found in the regression window (June 12–15). The regression may stem from a runtime or interpreter change not directly touching these files.

    Suggested reviewers / area contacts

    • Area lead (area-Diagnostics-coreclr): @steveisok
    • Area owners: @tommcdon, @dotnet/dotnet-diag
    • Already cc'd by @jkotas: @lateralusX (interpreter/runtime async expert)

    Filed by ci-failure-fix, which attempts validated fixes for [ci-scan] Known Build Errors and otherwise loops in owners. Comment here or on the workflow file to suggest changes; ci-failure-scan-feedback reads in-scope feedback daily and opens (or updates) a PR with prompt edits.

    Note

    🔒 Integrity filter blocked 6 items

    The following items were blocked because they don't meet the GitHub integrity level.

    • #128501 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #104998 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #104750 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #97491 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #76276 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • [ci-scan] Test failure: CustomAttributeDecoderTests.TestCustomAttributeDecoderGenericUsingReflection on maccatalyst #128450 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

    To allow these resources, lower min-integrity in your GitHub frontmatter:

    tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

    Generated by CI Outer-Loop Failure Fixer · ● 30M · ◷

  7. lateralusX commented on Jul 8, 2026

    @lateralusX
    lateralusX
    on Jul 8, 2026
    Member

    Should have been fixed by #129978.

  8. lateralusX
    closed this as completedon Jul 10, 2026
  9. dotnet-policy-service
    removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 10, 2026
  10. github-actions
    locked and limited conversation to collaborators on Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsarea-Diagnostics-coreclrblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions