Skip to content

[CI] XPackRestIT test {p0=migrate/20_reindex_status/Test Reindex With Existing Data Stream} failing #126769

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

Closed
elasticsearchmachine opened this issue Apr 14, 2025 · 3 comments · Fixed by #126942
Assignees
Labels
:Data Management/Data streams Data streams and their lifecycles needs:risk Requires assignment of a risk label (low, medium, blocker) 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:yamlRestTest" --tests "org.elasticsearch.xpack.test.rest.XPackRestIT.test {p0=migrate/20_reindex_status/Test Reindex With Existing Data Stream}" -Dtests.seed=821143916AB3F90C -Dtests.locale=fr-BF -Dtests.timezone=America/Cayenne -Druntime.java=24

Applicable branches:
9.0

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: Failure at [migrate/20_reindex_status:63]: 
Expected: <true>
     but: was <false>

Issue Reasons:

  • [9.0] 8 failures in test test {p0=migrate/20_reindex_status/Test Reindex With Existing Data Stream} (1.1% fail rate in 698 executions)
  • [9.0] 2 failures in step part3 (8.7% fail rate in 23 executions)
  • [9.0] 2 failures in step part-3 (9.5% fail rate in 21 executions)
  • [9.0] 2 failures in step openjdk21_checkpart3_java-fips-matrix (11.1% fail rate in 18 executions)
  • [9.0] 2 failures in pipeline elasticsearch-intake (7.7% fail rate in 26 executions)
  • [9.0] 2 failures in pipeline elasticsearch-pull-request (9.5% fail rate in 21 executions)
  • [9.0] 4 failures in pipeline elasticsearch-periodic (21.1% 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 :Search Relevance/Ranking Scoring, rescoring, rank evaluation. >test-failure Triaged test failures from CI labels Apr 14, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 9.0

Mute Reasons:

  • [9.0] 8 failures in test test {p0=migrate/20_reindex_status/Test Reindex With Existing Data Stream} (1.1% fail rate in 698 executions)
  • [9.0] 2 failures in step part3 (8.7% fail rate in 23 executions)
  • [9.0] 2 failures in step part-3 (9.5% fail rate in 21 executions)
  • [9.0] 2 failures in step openjdk21_checkpart3_java-fips-matrix (11.1% fail rate in 18 executions)
  • [9.0] 2 failures in pipeline elasticsearch-intake (7.7% fail rate in 26 executions)
  • [9.0] 2 failures in pipeline elasticsearch-pull-request (9.5% fail rate in 21 executions)
  • [9.0] 4 failures in pipeline elasticsearch-periodic (21.1% fail rate in 19 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Apr 14, 2025
…0_reindex_status/Test Reindex With Existing Data Stream} #126769
@elasticsearchmachine elasticsearchmachine added needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Apr 14, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@benwtrent benwtrent added :Data Management/Data streams Data streams and their lifecycles and removed :Search Relevance/Ranking Scoring, rescoring, rank evaluation. labels Apr 14, 2025
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team and removed Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels Apr 14, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

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 needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Data Management Meta label for data/management team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants