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] CoreWithSecurityClientYamlTestSuiteIT test {yaml=nodes.stats/11_indices_metrics/Metric - blank for indices shard_stats} failing #121131

Open
elasticsearchmachine opened this issue Jan 29, 2025 · 1 comment · May be fixed by #121296
Open

[CI] CoreWithSecurityClientYamlTestSuiteIT test {yaml=nodes.stats/11_indices_metrics/Metric - blank for indices shard_stats} failing #121131

elasticsearchmachine opened this issue Jan 29, 2025 · 1 comment · May be fixed by #121296
Assignees
@slobodanadamovic
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:qa:core-rest-tests-with-security:yamlRestTest" --tests "org.elasticsearch.xpack.security.CoreWithSecurityClientYamlTestSuiteIT" -Dtests.method="test {yaml=nodes.stats/11_indices_metrics/Metric - blank for indices shard_stats}" -Dtests.seed=2DEDA05E6ED854A0 -Dtests.locale=ne -Dtests.timezone=America/Ojinaga -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [nodes.stats/11_indices_metrics:343]: 
Expected: <0>
     but: was <1>

Issue Reasons:

  • [8.x] 2 failures in test test {yaml=nodes.stats/11_indices_metrics/Metric - blank for indices shard_stats} (1.1% fail rate in 190 executions)
  • [8.x] 2 failures in pipeline elasticsearch-periodic-platform-support (50.0% fail rate in 4 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 labels Jan 29, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 29, 2025
@dakrone dakrone 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 Jan 29, 2025
@slobodanadamovic slobodanadamovic self-assigned this Jan 30, 2025
@slobodanadamovic slobodanadamovic linked a pull request Jan 30, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@slobodanadamovic slobodanadamovic

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.

Unmute and fix tests slobodanadamovic/elasticsearch
3 participants
@dakrone @slobodanadamovic @elasticsearchmachine