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] ReindexDatastreamIndexTransportActionIT testFailIfReadBlockSet failing #122123

Open
elasticsearchmachine opened this issue Feb 8, 2025 · 2 comments
Labels
:Data Management/Data streams Data streams and their lifecycles medium-risk An open issue or test failure that is a medium 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:plugin:migrate:internalClusterTest" --tests "org.elasticsearch.xpack.migrate.action.ReindexDatastreamIndexTransportActionIT.testFailIfReadBlockSet" -Dtests.seed=837C0E29C0A794A5 -Dtests.locale=pt-CV -Dtests.timezone=Etc/GMT-6 -Druntime.java=23

Applicable branches:
9.0

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: All incoming requests on node [node_s1] should have finished. Expected 0 bytes for requests in-flight but got 298 bytes; pending tasks [[]]

Issue Reasons:

  • [9.0] 2 consecutive failures in test testFailIfReadBlockSet
  • [9.0] 11 failures in test testFailIfReadBlockSet (3.2% fail rate in 342 executions)
  • [9.0] 2 failures in step openjdk21_checkpart2_java-fips-matrix (22.2% fail rate in 9 executions)
  • [9.0] 4 failures in step part-2 (6.9% fail rate in 58 executions)
  • [9.0] 2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)
  • [9.0] 3 failures in pipeline elasticsearch-periodic (33.3% fail rate in 9 executions)
  • [9.0] 4 failures in pipeline elasticsearch-pull-request (7.0% fail rate in 57 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 Feb 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 9.0

Mute Reasons:

  • [9.0] 2 consecutive failures in test testFailIfReadBlockSet
  • [9.0] 11 failures in test testFailIfReadBlockSet (3.2% fail rate in 342 executions)
  • [9.0] 2 failures in step openjdk21_checkpart2_java-fips-matrix (22.2% fail rate in 9 executions)
  • [9.0] 4 failures in step part-2 (6.9% fail rate in 58 executions)
  • [9.0] 2 failures in pipeline elasticsearch-periodic-platform-support (20.0% fail rate in 10 executions)
  • [9.0] 3 failures in pipeline elasticsearch-periodic (33.3% fail rate in 9 executions)
  • [9.0] 4 failures in pipeline elasticsearch-pull-request (7.0% fail rate in 57 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Feb 8, 2025
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 8, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@dakrone dakrone added medium-risk An open issue or test failure that is a medium risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Data streams Data streams and their lifecycles medium-risk An open issue or test failure that is a medium risk to future releases Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

2 participants