Skip to content
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

[CI] CrossClusterAsyncQueryIT testStopQueryLocal failing #121487

Closed
elasticsearchmachine opened this issue Feb 1, 2025 · 6 comments
Closed

[CI] CrossClusterAsyncQueryIT testStopQueryLocal failing #121487

elasticsearchmachine opened this issue Feb 1, 2025 · 6 comments
Assignees
Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium risk to future releases :Search Foundations/CCS Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >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.CrossClusterAsyncQueryIT.testStopQueryLocal" -Dtests.seed=9118AB4453C6411D -Dtests.locale=fr-PM -Dtests.timezone=Africa/Ouagadougou -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: not <running>
     but: was <running>

Issue Reasons:

  • [main] 3 failures in test testStopQueryLocal (0.9% fail rate in 327 executions)
  • [main] 2 failures in step part-3 (1.5% fail rate in 132 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.5% fail rate in 131 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 Feb 1, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testStopQueryLocal (0.9% fail rate in 327 executions)
  • [main] 2 failures in step part-3 (1.5% fail rate in 132 executions)
  • [main] 2 failures in pipeline elasticsearch-pull-request (1.5% fail rate in 131 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 Feb 1, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added the Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch label Feb 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-foundations (Team:Search Foundations)

@alex-spies
Copy link
Contributor

@smalyshev , I hope it's okay I assign you to this, as you recently made changes to this test.

@alex-spies
Copy link
Contributor

@smalyshev , I don't understand the test well enough to properly assess the risk - I assume this is not a blocker, but cannot say if this should be low risk. I'll go with medium - please correct me if you disagree!

@alex-spies alex-spies added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 3, 2025
@smalyshev
Copy link
Contributor

Same as #121672 but pre-refactoring. Closing this one - will continue with the other one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL medium-risk An open issue or test failure that is a medium risk to future releases :Search Foundations/CCS Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

3 participants