Skip to content

[CI] ForkIT testWithStatsSimple failing #126607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
elasticsearchmachine opened this issue Apr 10, 2025 · 3 comments · Fixed by #126706
Closed

[CI] ForkIT testWithStatsSimple failing #126607

elasticsearchmachine opened this issue Apr 10, 2025 · 3 comments · Fixed by #126706
Assignees
Labels
:Analytics/ES|QL AKA ESQL low-risk An open issue or test failure that is a low risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:esql:internalClusterTest" --tests "org.elasticsearch.xpack.esql.action.ForkIT.testWithStatsSimple" -Dtests.seed=DD6C010AF787828F -Dtests.jvm.argline="-Des.entitlements.enabled=false" -Dtests.locale=en-IM -Dtests.timezone=NST -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <[[fork1, 6, [1, 2, 3, 4, 5, 6], null], [fork2, null, null, 2]]>
     but: was <[[fork1, 6, [5, 4, 3, 6, 1, 2], null], [fork2, null, null, 2]]>

Issue Reasons:

  • [main] 3 failures in test testWithStatsSimple (13.6% fail rate in 22 executions)
  • [main] 2 failures in step part-3 (10.5% fail rate in 19 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (10.5% fail rate in 19 executions)

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

@elasticsearchmachine elasticsearchmachine added :Analytics/ES|QL AKA ESQL >test-failure Triaged test failures from CI labels Apr 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testWithStatsSimple (13.6% fail rate in 22 executions)
  • [main] 2 failures in step part-3 (10.5% fail rate in 19 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (10.5% fail rate in 19 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@ivancea ivancea assigned ivancea and ioanatia and unassigned ivancea Apr 11, 2025
@ioanatia
Copy link
Contributor

@bpintea fixed this already #126604

I will unmute the test

@bpintea bpintea added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL low-risk An open issue or test failure that is a low risk to future releases Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants