Skip to content

[CI] EsqlSpecIT test {fork.ForkWithWhereSortDescAndLimit SYNC} failing #127326

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 24, 2025 · 4 comments
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:qa:server:single-node:javaRestTest" --tests "org.elasticsearch.xpack.esql.qa.single_node.EsqlSpecIT" -Dtests.method="test {fork.ForkWithWhereSortDescAndLimit SYNC}" -Dtests.seed=AC3C2A6B0A8A46D8 -Dtests.jvm.argline="-Des.entitlements.enabled=true" -Dtests.locale=luy -Dtests.timezone=Asia/Khandyga -Druntime.java=21

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Expected a map containing
   lt_1s: <35>
   lt_1d: <0>
  lt_10s: <1>
   gt_1d: <0>
   lt_1h: <0>
 lt_10ms: expected <1217> but was <1218>
   lt_1m: <0>
  lt_10h: <0>
  lt_10m: <0>
lt_100ms: expected <1055> but was <1054>

Issue Reasons:

  • [main] 4 failures in test test {fork.ForkWithWhereSortDescAndLimit SYNC} (0.5% fail rate in 731 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (15.4% fail rate in 13 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 24, 2025
elasticsearchmachine added a commit that referenced this issue Apr 24, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 4 failures in test test {fork.ForkWithWhereSortDescAndLimit SYNC} (0.5% fail rate in 731 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (15.4% fail rate in 13 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 24, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@fang-xing-esql
Copy link
Member

It looks similar as #127063

@fang-xing-esql fang-xing-esql 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 24, 2025
@ioanatia ioanatia self-assigned this Apr 24, 2025
@ioanatia
Copy link
Contributor

ioanatia commented Apr 28, 2025

fixed with #127328
unmuted with #127455

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

No branches or pull requests

3 participants