Skip to content

[CI] XpackWithMultipleProjectsClientYamlTestSuiteIT class failing #127433

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
Closed
elasticsearchmachine opened this issue Apr 26, 2025 · 2 comments · Fixed by #127699
Closed

[CI] XpackWithMultipleProjectsClientYamlTestSuiteIT class failing #127433

elasticsearchmachine opened this issue Apr 26, 2025 · 2 comments · Fixed by #127699
Assignees
@nielsbauman
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:

undefined

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [main] 19 failures in class org.elasticsearch.multiproject.test.XpackWithMultipleProjectsClientYamlTestSuiteIT (3.3% fail rate in 568 executions)
  • [main] 4 failures in step part-2 (1.7% fail rate in 231 executions)
  • [main] 2 failures in step encryption-at-rest (22.2% fail rate in 9 executions)
  • [main] 2 failures in step single-processor-node-tests (33.3% fail rate in 6 executions)
  • [main] 4 failures in step concurrent-search-tests (44.4% fail rate in 9 executions)
  • [main] 2 failures in step almalinux-8_platform-support-unix (22.2% fail rate in 9 executions)
  • [main] 2 failures in step rhel-8_platform-support-unix (25.0% fail rate in 8 executions)
  • [main] 2 failures in step rocky-8_platform-support-unix (28.6% fail rate in 7 executions)
  • [main] 6 failures in pipeline elasticsearch-periodic-platform-support (60.0% fail rate in 10 executions)
  • [main] 5 failures in pipeline elasticsearch-periodic (50.0% fail rate in 10 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (1.7% fail rate in 231 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 Apr 26, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@nielsbauman nielsbauman self-assigned this Apr 29, 2025
@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 Apr 29, 2025
@nielsbauman
Copy link
Contributor

All these test failures seemed to have been caused by timeouts. My hunch is that this was caused by Make IndexTemplateRegistry project-aware #126986, which was merged a few days ago, around the same time the average runtime of this test suite significantly increases: https://es-delivery-stats.elastic.dev/app/r/s/BnqIq

Image

@nielsbauman nielsbauman mentioned this issue May 4, 2025
Closed
nielsbauman added a commit to nielsbauman/elasticsearch that referenced this issue May 5, 2025
@nielsbauman
Bump the MP x-pack YAML test suite timeout to 60m
d4bebd9 
After the `IndexTemplateRegistry` was made project-aware in elastic#126986,
we were seeing timeouts of the MP version of the x-pack YAML test suite.
The original version has a timeout of 60 minutes but the MP-version
still had a timeout of 30 minutes. We've gotten away with that
difference because there are still tests on the blacklist for the MP
version, but now that we're making more and more features project-aware,
we need to align the timeout.

Fixes elastic#127433
@nielsbauman nielsbauman mentioned this issue May 5, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nielsbauman nielsbauman

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

Successfully merging a pull request may close this issue.

Bump the MP x-pack YAML test suite timeout to 60m nielsbauman/elasticsearch
2 participants
@nielsbauman @elasticsearchmachine