Skip to content

[Crossgen2 CI] jit64_5 work item failing in R2R outerloop on osx-arm64 #55

@github-actions

Description

@github-actions

Failure Details

  • Pipeline: runtime-coreclr crossgen2 outerloop
  • Build: 1394432
  • Failed Job: coreclr Pri1 Runtime Tests Run R2R osx arm64 checked
  • Configuration: osx-arm64 R2R checked
  • Error Category: test-failure

Failing Tests

Test Name Platform Error Type
jit64_5 (Helix work item) osx-arm64 Test failure

Error Output

The jit64_5 Helix work item failed in the R2R outerloop job on osx-arm64. This failure does NOT appear in the runtime pipeline, confirming it is crossgen2/R2R-specific. Note: jit64_3 is separately tracked in issue #23 (windows-x86 composite OOM).

Error details
Work item jit64_5 in job 2a22709a-284e-416f-b767-3f2405382959 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/2a22709a-284e-416f-b767-3f2405382959/workitems/jit64_5/console

Job: coreclr  Pri1 Runtime Tests Run R2R osx arm64 checked
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1394432&view=logs&j=99f15f99-448d-5593-a271-dbdf553789a6

Helix Details

Cross-Reference

  • Runtime pipeline: NOT found in recent runtime builds (checked 1394540, 1393668). Crossgen2 R2R-specific.
  • Previous outerloop builds: NOT present in previous outerloop build 1392513, indicating a new regression.
  • Related: #23 tracks jit64_3 on windows-x86 composite (OOM) — different work item group.

Recommended Action

This failure requires deeper investigation. Please disable the failing test by adding an [ActiveIssue] attribute referencing this issue:

  • The jit64_5 work item contains tests from the src/tests/ directory tree. Check the Helix console log to find the specific failing test(s).
  • Add [ActiveIssue("https://github.com/jtschuster/runtime/issues/ISSUE_NUMBER")] to the test method or class.
  • Since this only fails in R2R mode on osx-arm64, target R2R/crossgen2 configurations on that platform if possible.

Generated by Crossgen2 CI Failure Triage ·

  • expires on May 24, 2026, 2:34 PM UTC

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions