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] SystemResourceSnapshotIT class failing #124920

Closed
elasticsearchmachine opened this issue Mar 14, 2025 · 4 comments
Closed

[CI] SystemResourceSnapshotIT class failing #124920

elasticsearchmachine opened this issue Mar 14, 2025 · 4 comments
Assignees
@JVerwolf
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Mar 14, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

gradlew ":server:internalClusterTest" --tests "org.elasticsearch.snapshots.SystemResourceSnapshotIT.testDeletedDatastreamIsRestorable" -Dtests.seed=6ABB43D270B066D3 -Dtests.locale=fr-GN -Dtests.timezone=America/Dawson -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.elasticsearch.ResourceNotFoundException: data streams [.test-system-data-stream] not found

Issue Reasons:

  • [main] 39 failures in class org.elasticsearch.snapshots.SystemResourceSnapshotIT (52.0% fail rate in 75 executions)
  • [main] 21 failures in step part-1 (53.8% fail rate in 39 executions)
  • [main] 3 failures in step part-1-entitlements (42.9% fail rate in 7 executions)
  • [main] 2 failures in step part1 (25.0% fail rate in 8 executions)
  • [main] 22 failures in pipeline elasticsearch-pull-request (57.9% fail rate in 38 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (25.0% fail rate in 8 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Mar 14, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@JVerwolf JVerwolf self-assigned this Mar 24, 2025
@ldematte
Copy link
Contributor

@JVerwolf I see you are looking at this - do you already have an idea of the risk?

@JVerwolf JVerwolf 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 28, 2025
@JVerwolf
Copy link
Contributor

JVerwolf commented Mar 28, 2025 •
edited
Loading

@ldematte I think these were all fixed by these PRs: #124931 and #124924

Just to confirm, these SystemResourceSnapshotIT are currently not-muted and running on main, right? (I took a look and I don't see them muted anywhere, but want to confirm). If so, we can safely close this issue as it was fixed by the above PR.

@JVerwolf
Copy link
Contributor

Fixed by #124924

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JVerwolf JVerwolf

Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ldematte @JVerwolf @elasticsearchmachine