Skip to content

[CI] TransportVersionValidationFuncTest latest files cannot change base id failing #133132

@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

null

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.spockframework.runtime.ConditionNotSatisfiedError: Condition not satisfied:

normalized(givenOutput).contains(normalized(expected))
|          |            |        |          |
|          |            false    |          Transport version definition file [myserver/src/main/resources/transport/definitions/named/existing_92.csv] modifies existing patch id from 8012001 to 8012002
|          |                     Transport version definition file [myserver/src/main/resources/transport/definitions/named/existing_92.csv] modifies existing patch id from 8012001 to 8012002
|          =======================================
|          Elasticsearch Build Hamster says Hello!
|            Gradle Version        : 9.0.0
|            OS Info               : Windows Server 2025 10.0 (amd64)
|            JDK Version           : 21.0.7+6-LTS (Eclipse Temurin)
|            JAVA_HOME             : C:/Users/buildkite/.gradle/jdks/eclipse_adoptium-21-amd64-windows.2
|            Random Testing Seed   
[truncated]

Issue Reasons:

  • [main] 2 consecutive failures in test latest files cannot change base id
  • [main] 3 consecutive failures in step windows-2025_checkpart1_platform-support-windows
  • [main] 3 consecutive failures in step windows-2022_checkpart1_platform-support-windows
  • [main] 3 consecutive failures in pipeline elasticsearch-periodic-platform-support
  • [main] 9 failures in test latest files cannot change base id (31.0% fail rate in 29 executions)
  • [main] 3 failures in step windows-2025_checkpart1_platform-support-windows (100.0% fail rate in 3 executions)
  • [main] 3 failures in step windows-2022_checkpart1_platform-support-windows (100.0% fail rate in 3 executions)
  • [main] 3 failures in step part-1 (16.7% fail rate in 18 executions)
  • [main] 3 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 3 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (16.7% fail rate in 18 executions)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Core/Infra/Transport APITransport client API>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