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] ClusterStatsRemoteIT testRemoteClusterStats failing #113822

Closed
elasticsearchmachine opened this issue Sep 30, 2024 · 3 comments · Fixed by #113824
Closed

[CI] ClusterStatsRemoteIT testRemoteClusterStats failing #113822

elasticsearchmachine opened this issue Sep 30, 2024 · 3 comments · Fixed by #113824
Assignees
@smalyshev
Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Sep 30, 2024 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":server:internalClusterTest" --tests "org.elasticsearch.action.admin.cluster.stats.ClusterStatsRemoteIT.testRemoteClusterStats" -Dtests.seed=106793A356416C43 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=en-PN -Dtests.timezone=Pacific/Wake -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <3>
     but: was <0>

Issue Reasons:

  • [main] 3 failures in test testRemoteClusterStats (18.8% fail rate in 16 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testRemoteClusterStats (14.3% fail rate in 14 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Sep 30, 2024
@elasticsearchmachine
Mute org.elasticsearch.action.admin.cluster.stats.ClusterStatsRemoteI…
0a4fd0c 
…T testRemoteClusterStats #113822
@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch labels Sep 30, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-foundations (Team:Search Foundations)

@smalyshev smalyshev self-assigned this Sep 30, 2024
@smalyshev
Copy link
Contributor

Oh yes, forgot to disable it when the flag is off :\ sigh...

@smalyshev smalyshev mentioned this issue Sep 30, 2024
Merged
@smalyshev smalyshev added the low-risk An open issue or test failure that is a low risk to future releases label Sep 30, 2024
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Sep 30, 2024
matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this issue Oct 4, 2024
@elasticsearchmachine @matthewabbott
Mute org.elasticsearch.action.admin.cluster.stats.ClusterStatsRemoteI…
aef1824 
…T testRemoteClusterStats elastic#113822
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@smalyshev smalyshev

Labels
low-risk An open issue or test failure that is a low risk to future releases :Search Foundations/CCS Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix test: create enough nodes to make cluster always be able to go green smalyshev/elasticsearch
2 participants
@smalyshev @elasticsearchmachine