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.

Sign up for GitHub

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

Jump to bottom

[CI] XPackRestIT test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version} failing #116448

Open
elasticsearchmachine opened this issue Nov 7, 2024 · 3 comments · May be fixed by #116470
Open

[CI] XPackRestIT test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version} failing #116448

elasticsearchmachine opened this issue Nov 7, 2024 · 3 comments · May be fixed by #116470
Assignees
@luigidellaquila
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

elasticsearchmachine commented Nov 7, 2024 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:yamlRestTest" --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version}" -Dtests.seed=70300202F4AFCC52 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=es-CR -Dtests.timezone=Asia/Oral -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [esql/60_usage:165]: field [esql.functions] doesn't have length [118]
Expected: <118>
     but: was <116>

Issue Reasons:

  • [8.x] 4 consecutive failures in test test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version}
  • [8.x] 4 consecutive failures in step release-tests
  • [8.x] 4 consecutive failures in pipeline elasticsearch-periodic
  • [8.x] 4 failures in test test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version} (100.0% fail rate in 4 executions)
  • [8.x] 4 failures in step release-tests (100.0% fail rate in 4 executions)
  • [8.x] 4 failures in pipeline elasticsearch-periodic (100.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Search Relevance/Ranking Scoring, rescoring, rank evaluation. >test-failure Triaged test failures from CI labels Nov 7, 2024
elasticsearchmachine added a commit that referenced this issue Nov 7, 2024
@elasticsearchmachine
Mute org.elasticsearch.xpack.test.rest.XPackRestIT test {p0=esql/60_u…
b3d5dbd 
…sage/Basic ESQL usage output (telemetry) non-snapshot version} #116448
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step part-3
  • [main] 3 consecutive failures in step rest-compatibility
  • [main] 6 failures in test test {p0=esql/60_usage/Basic ESQL usage output (telemetry) non-snapshot version} (24.0% fail rate in 25 executions)
  • [main] 2 failures in step part-3 (100.0% fail rate in 2 executions)
  • [main] 3 failures in step rest-compatibility (100.0% fail rate in 3 executions)
  • [main] 3 failures in pipeline elasticsearch-pull-request (33.3% fail rate in 9 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Nov 7, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@luigidellaquila luigidellaquila added :Analytics/ES|QL AKA ESQL low-risk An open issue or test failure that is a low risk to future releases and removed :Search Relevance/Ranking Scoring, rescoring, rank evaluation. needs:risk Requires assignment of a risk label (low, medium, blocker) labels Nov 8, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Nov 8, 2024
@luigidellaquila luigidellaquila linked a pull request Nov 8, 2024 that will close this issue
Open
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine removed the Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch label Nov 8, 2024
@luigidellaquila luigidellaquila self-assigned this Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@luigidellaquila luigidellaquila

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
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ES|QL: Fix funciton Telemetry tests luigidellaquila/elasticsearch
2 participants
@luigidellaquila @elasticsearchmachine