Skip to content

[CI] DefaultMethodHandleResolverTests testDefaultResolverBuildsWorkingMethodHandle failing #155012

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: GetCurrentProcessId not found in default linker lookup

Issue Reasons:

  • [main] 2 consecutive failures in step windows-2022_checkpart6_platform-support-windows
  • [main] 2 consecutive failures in step windows-2025_checkpart6_platform-support-windows
  • [main] 4 failures in test testDefaultResolverBuildsWorkingMethodHandle (6.5% fail rate in 62 executions)
  • [main] 2 failures in step windows-2022_checkpart6_platform-support-windows (100.0% fail rate in 2 executions)
  • [main] 2 failures in step windows-2025_checkpart6_platform-support-windows (100.0% fail rate in 2 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-core-infra.

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Core/Infra/CoreCore issues without another label>test-failureTriaged test failures from CITeam:Core/InfraMeta label for core/infra teamneeds:riskRequires assignment of a risk label (low, medium, blocker)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions