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] AggregationsTests testFromXContentWithRandomFields failing #121188

Open
elasticsearchmachine opened this issue Jan 29, 2025 · 2 comments
Open

[CI] AggregationsTests testFromXContentWithRandomFields failing #121188

elasticsearchmachine opened this issue Jan 29, 2025 · 2 comments
Labels
:Analytics/Aggregations Aggregations 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 ':server:test' --tests "org.elasticsearch.search.aggregations.AggregationsTests.testFromXContentWithRandomFields" -Dtests.seed=B443163DF58A2A8B -Dtests.locale=ar-IQ -Dtests.timezone=Africa/Gaborone -Druntime.java=22

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

com.fasterxml.jackson.dataformat.yaml.JacksonYAMLParseException: The incoming YAML document exceeds the limit: 3145728 code points.
 at [Source: (ByteArrayInputStream); line: 64122, column: 53]

Issue Reasons:

  • [7.17] 2 failures in test testFromXContentWithRandomFields (0.3% fail rate in 608 executions)
  • [7.17] 2 failures in pipeline elasticsearch-periodic-platform-support (13.3% fail rate in 15 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Analytics/Aggregations Aggregations >test-failure Triaged test failures from CI Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 29, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@nik9000 nik9000 added the low-risk An open issue or test failure that is a low risk to future releases label Jan 29, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Jan 29, 2025
@nik9000
Copy link
Member

nik9000 commented Jan 29, 2025

This test doesn't exist in main and it seems to be a data generation thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Analytics/Aggregations Aggregations 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

No branches or pull requests
2 participants
@nik9000 @elasticsearchmachine