Skip to content

[CI] LuceneTopNSourceOperatorTests testShardDataPartitioningWithCranky failing #133607

Closed
#133601
Closed
[CI] LuceneTopNSourceOperatorTests testShardDataPartitioningWithCranky failing#133607
#133601
Labels
:Analytics/ES|QLAKA ESQL>test-failureTriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)needs:riskRequires assignment of a risk label (low, medium, blocker)

Description

@elasticsearchmachine
elasticsearchmachine
opened on Aug 26, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:compute:test" --tests "org.elasticsearch.compute.lucene.LuceneTopNSourceOperatorTests.testShardDataPartitioningWithCranky" -Dtests.seed=475683211F630D3 -Dtests.configure_test_clusters_with_one_processor=true -Dtests.locale=th-Thai-TH -Dtests.timezone=America/Kentucky/Louisville -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: sameInstance(<Single[index=0, refCounted=org.elasticsearch.compute.lucene.LuceneTopNSourceOperatorTests$1@77d784c5]>)
     but: was <Single[index=0, refCounted=org.elasticsearch.compute.lucene.LuceneTopNSourceOperatorTests$1@77d784c5]>

Issue Reasons:

  • [main] 6 failures in test testShardDataPartitioningWithCranky (2.4% fail rate in 246 executions)
  • [main] 4 failures in step part-3 (3.2% fail rate in 124 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (3.3% fail rate in 120 executions)

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

Activity

  1. elasticsearchmachine
    added
    >test-failureTriaged test failures from CI
    :Analytics/ES|QLAKA ESQL
    on Aug 26, 2025

  2. elasticsearchmachine commented on Aug 26, 2025

    @elasticsearchmachine
    elasticsearchmachine
    on Aug 26, 2025
    CollaboratorAuthor

    This has been muted on branch main

    Mute Reasons:

    • [main] 2 consecutive failures in test testShardDataPartitioningWithCranky
    • [main] 5 failures in test testShardDataPartitioningWithCranky (2.1% fail rate in 243 executions)
    • [main] 4 failures in step part-3 (3.3% fail rate in 123 executions)
    • [main] 4 failures in pipeline elasticsearch-pull-request (3.4% fail rate in 119 executions)

    Build Scans:

  3. elasticsearchmachine
    added a commit that references this issue on Aug 26, 2025

    Mute org.elasticsearch.compute.lucene.LuceneTopNSourceOperatorTests t…

    07532e3
  4. elasticsearchmachine
    added
    Team:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)
    needs:riskRequires assignment of a risk label (low, medium, blocker)
    on Aug 26, 2025

  5. elasticsearchmachine commented on Aug 26, 2025

    @elasticsearchmachine
    elasticsearchmachine
    on Aug 26, 2025
    CollaboratorAuthor

    Pinging @elastic/es-analytical-engine (Team:Analytics)

  6. nik9000
    closed this as completedin #133601on Aug 27, 2025
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

    :Analytics/ES|QLAKA ESQL>test-failureTriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)needs: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