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.

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

[CI] NodeStatsTests testChunking failing #113139

Closed
elasticsearchmachine opened this issue Sep 18, 2024 · 4 comments · Fixed by #115929
Closed

[CI] NodeStatsTests testChunking failing #113139

elasticsearchmachine opened this issue Sep 18, 2024 · 4 comments · Fixed by #115929
Assignees
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

Build Scans:

Reproduction Line:

./gradlew ":server:test" --tests "org.elasticsearch.action.admin.cluster.node.stats.NodeStatsTests.testChunking" -Dtests.seed=2D92AD5B737DA09E -Dtests.locale=pt-LU -Dtests.timezone=Europe/Nicosia -Druntime.java=22

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: expected:<233> but was:<232>

Issue Reasons:

  • [main] 3 failures in test testChunking (1.3% fail rate in 240 executions)
  • [main] 2 failures in step part1 (4.0% fail rate in 50 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (4.0% fail rate in 50 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :StorageEngine/Mapping The storage related side of mappings >test-failure Triaged test failures from CI labels Sep 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 3 failures in test testChunking (1.3% fail rate in 240 executions)
  • [main] 2 failures in step part1 (4.0% fail rate in 50 executions)
  • [main] 2 failures in pipeline elasticsearch-intake (4.0% fail rate in 50 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:StorageEngine needs:risk Requires assignment of a risk label (low, medium, blocker) labels Sep 18, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-storage-engine (Team:StorageEngine)

@dnhatn dnhatn self-assigned this Sep 18, 2024
@dnhatn
Copy link
Member

dnhatn commented Oct 29, 2024

I took a quick look, and the test failure appears to be triggered by #113139, so I’m re-labeling the issue. @thecoop, would you mind taking a look? Thanks!

@dnhatn dnhatn added :Core/Infra/Core Core issues without another label and removed Team:StorageEngine :StorageEngine/Mapping The storage related side of mappings labels Oct 29, 2024
@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Oct 29, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

@dnhatn dnhatn assigned thecoop and unassigned dnhatn Oct 29, 2024
@dnhatn dnhatn 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 Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging a pull request may close this issue.

3 participants