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=data_stream/80_resolve_index_data_streams/Resolve index with hidden and closed indices} failing #125897

Closed
elasticsearchmachine opened this issue Mar 29, 2025 · 2 comments
Closed

[CI] XPackRestIT test {p0=data_stream/80_resolve_index_data_streams/Resolve index with hidden and closed indices} failing #125897

elasticsearchmachine opened this issue Mar 29, 2025 · 2 comments
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:

./gradlew ":x-pack:plugin:yamlRestTestV7CompatTest" --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=data_stream/80_resolve_index_data_streams/Resolve index with hidden and closed indices}" -Dtests.seed=D3D01922EAC1F2E3 -Dtests.locale=lb -Dtests.timezone=Europe/Astrakhan -Druntime.java=23

Applicable branches:
8.18

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [data_stream/80_resolve_index_data_streams:261]: 
Expected: "test_index1"
     but: was ".security-7"

Issue Reasons:

  • [8.18] 2 failures in test test {p0=data_stream/80_resolve_index_data_streams/Resolve index with hidden and closed indices} (1.0% fail rate in 199 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 Mar 29, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

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

nielsbauman commented Mar 31, 2025 •
edited
Loading

Fixed by #125949 (which was just a backport of #125682)

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

No branches or pull requests
2 participants
@nielsbauman @elasticsearchmachine