Skip to content

[CI] RepositoriesFileSettingsIT testSettingsApplied failing #126748

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
Open
elasticsearchmachine opened this issue Apr 13, 2025 · 2 comments
Open

[CI] RepositoriesFileSettingsIT testSettingsApplied failing #126748

elasticsearchmachine opened this issue Apr 13, 2025 · 2 comments
Assignees
@prdoyle
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 Apr 13, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.reservedstate.service.RepositoriesFileSettingsIT.testSettingsApplied" -Dtests.seed=EDAFE03E8ECCF209 -Dtests.locale=ff-SN -Dtests.timezone=Etc/Greenwich -Druntime.java=23

Applicable branches:
8.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.util.concurrent.ExecutionException: org.elasticsearch.transport.RemoteTransportException: [node_t1][127.0.0.1:19632][cluster:admin/repository/get]

Issue Reasons:

  • [8.17] 5 failures in test testSettingsApplied (0.8% fail rate in 603 executions)
  • [8.17] 2 failures in step encryption-at-rest (10.0% fail rate in 20 executions)
  • [8.17] 2 failures in step almalinux-8-aarch64_checkpart1_platform-support-arm (10.5% fail rate in 19 executions)
  • [8.17] 2 failures in pipeline elasticsearch-periodic (10.0% fail rate in 20 executions)
  • [8.17] 3 failures in pipeline elasticsearch-periodic-platform-support (15.8% fail rate in 19 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 labels Apr 13, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added Team:Core/Infra Meta label for core/infra team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 13, 2025
@rjernst rjernst 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 19, 2025
@rjernst
Copy link
Member

rjernst commented Apr 19, 2025

@prdoyle it seems there still may be a timing issue in this test

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

@prdoyle prdoyle

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
@rjernst @prdoyle @elasticsearchmachine