Skip to content

[CI] IndexSortUpgradeIT testIndexSortForNumericTypes {upgradedNodes=2} failing #138129

@elasticsearchmachine

Description

@elasticsearchmachine

Build Scans:

Reproduction Line:

./gradlew ":qa:rolling-upgrade:v9.0.7#bwcTest" -Dtests.class="org.elasticsearch.upgrades.IndexSortUpgradeIT" -Dtests.method="testIndexSortForNumericTypes {upgradedNodes=2}" -Dtests.seed=F5C3D5FC3588ECDC -Dtests.bwc=true -Dtests.locale=bn-IN -Dtests.timezone=Africa/Algiers -Druntime.java=25

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.client.ResponseException: method [GET], host [http://[::1]:38263], URI [/index_int/_search], status line [HTTP/1.1 400 Bad Request]
{"error":{"root_cause":[],"type":"search_phase_execution_exception","reason":"","phase":"fetch","grouped":true,"failed_shards":[],"caused_by":{"type":"illegal_argument_exception","reason":"Can't sort on field [int_field]; the field has incompatible sort types: [INT] and [LONG] across shards!"}},"status":400}

Issue Reasons:

  • [main] 2 consecutive failures in step 9.0.7_bwc
  • [main] 7 failures in test testIndexSortForNumericTypes {upgradedNodes=2} (0.8% fail rate in 914 executions)
  • [main] 3 failures in step 9.0.7_bwc (37.5% fail rate in 8 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.4% fail rate in 140 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

    :Search Relevance/SearchCatch all for Search Relevance>test-failureTriaged test failures from CITeam:Search RelevanceMeta label for the Search Relevance team in Elasticsearchneeds: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