Skip to content

[CI] XpackWithMultipleProjectsClientYamlTestSuiteIT test {yaml=downsample/10_basic/Downsample failure} failing #127681

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 May 4, 2025 · 2 comments
Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

./gradlew ":x-pack:qa:multi-project:xpack-rest-tests-with-multiple-projects:yamlRestTest" --tests "org.elasticsearch.multiproject.test.XpackWithMultipleProjectsClientYamlTestSuiteIT.test {yaml=downsample/10_basic/Downsample failure}" -Dtests.seed=CFEC8E5B8072480B -Dtests.locale=gl -Dtests.timezone=Canada/Yukon -Druntime.java=24

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.Exception: Test abandoned because suite timeout was reached.

Issue Reasons:

  • [main] 2 failures in test test {yaml=downsample/10_basic/Downsample failure} (0.3% fail rate in 615 executions)
  • [main] 2 failures in pipeline elasticsearch-periodic-platform-support (14.3% fail rate in 14 executions)

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

@elasticsearchmachine elasticsearchmachine added :Data Management/Data streams Data streams and their lifecycles >test-failure Triaged test failures from CI Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 4, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-data-management (Team:Data Management)

@nielsbauman nielsbauman 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 May 4, 2025
@nielsbauman
Copy link
Contributor

Duplicate of #127433

@nielsbauman nielsbauman marked this as a duplicate of #127433 May 4, 2025
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Data streams Data streams and their lifecycles low-risk An open issue or test failure that is a low risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants