Skip to content

[CI] ShardBulkInferenceActionFilterIT testRestart {p0=true p1=true} failing #127595

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
Open
elasticsearchmachine opened this issue May 1, 2025 · 7 comments
Open

[CI] ShardBulkInferenceActionFilterIT testRestart {p0=true p1=true} failing #127595

elasticsearchmachine opened this issue May 1, 2025 · 7 comments
Labels
medium-risk An open issue or test failure that is a medium risk to future releases :Search Relevance/Search Catch all for Search Relevance :SearchOrg/Relevance Label for the Search (solution/org) Relevance team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented May 1, 2025 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:inference:internalClusterTest" --tests "org.elasticsearch.xpack.inference.action.filter.ShardBulkInferenceActionFilterIT.testRestart {p0=false p1=false}" -Dtests.seed=901A3137A084EE7A -Dtests.locale=ru-UA -Dtests.timezone=Antarctica/DumontDUrville -Druntime.java=24

Applicable branches:
8.19

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <91>
     but: was <88>

Issue Reasons:

  • [8.19] 4 failures in test testRestart {p0=true p1=true} (0.7% fail rate in 583 executions)
  • [8.19] 3 failures in pipeline elasticsearch-periodic-platform-support (17.6% fail rate in 17 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :ml Machine learning >test-failure Triaged test failures from CI labels May 1, 2025
elasticsearchmachine added a commit that referenced this issue May 1, 2025
@elasticsearchmachine
Mute org.elasticsearch.xpack.inference.action.filter.ShardBulkInferen…
0f46959 
…ceActionFilterIT testRestart {p0=true p1=true} #127595
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testRestart {p0=true p1=true} (0.9% fail rate in 222 executions)

Build Scans:

@elasticsearchmachine elasticsearchmachine added Team:ML Meta label for the ML team needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 1, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/ml-core (Team:ML)

@davidkyle
Copy link
Member

This reproduces with the reproduction line above. #127594, #127593 and #127592 appear to be the same

@davidkyle davidkyle added :Search Relevance/Search Catch all for Search Relevance and removed :ml Machine learning Team:ML Meta label for the ML team labels May 2, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@elasticsearchmachine elasticsearchmachine added the Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch label May 2, 2025
@davidkyle davidkyle removed >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) :Search Relevance/Search Catch all for Search Relevance labels May 2, 2025
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label and removed Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels May 2, 2025
@davidkyle davidkyle added >test-failure Triaged test failures from CI Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch and removed needs:triage Requires assignment of a team area label labels May 2, 2025
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label needs:risk Requires assignment of a risk label (low, medium, blocker) and removed Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch labels May 2, 2025
@davidkyle davidkyle added :Search Relevance/Search Catch all for Search Relevance >test-failure Triaged test failures from CI and removed >test-failure Triaged test failures from CI needs:triage Requires assignment of a team area label needs:risk Requires assignment of a risk label (low, medium, blocker) labels May 2, 2025
@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label May 2, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch label May 2, 2025
@benwtrent benwtrent added the :SearchOrg/Relevance Label for the Search (solution/org) Relevance team label May 2, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/search-eng (Team:SearchOrg)

@elasticsearchmachine
Copy link
Collaborator Author

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

@Mikep86 Mikep86 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 May 2, 2025
@Mikep86
Copy link
Contributor

Mikep86 commented May 2, 2025

Was not able to replicate this failure locally. Will take a closer look as time allows today, or worst case next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
medium-risk An open issue or test failure that is a medium risk to future releases :Search Relevance/Search Catch all for Search Relevance :SearchOrg/Relevance Label for the Search (solution/org) Relevance team Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davidkyle @benwtrent @Mikep86 @elasticsearchmachine