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] InferenceCrudIT testGet failing #114135

Closed
elasticsearchmachine opened this issue Oct 4, 2024 · 5 comments
Closed

[CI] InferenceCrudIT testGet failing #114135

elasticsearchmachine opened this issue Oct 4, 2024 · 5 comments
Assignees
Labels
low-risk An open issue or test failure that is a low risk to future releases :ml Machine learning Team:ML Meta label for the ML team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Oct 4, 2024

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:inference:qa:inference-service-tests:javaRestTest" --tests "org.elasticsearch.xpack.inference.InferenceCrudIT.testGet" -Dtests.seed=D210074B9559AFD7 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=fr-MG -Dtests.timezone=Europe/Athens -Druntime.java=22

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: a collection with size <9>
     but: collection size was <10>

Issue Reasons:

  • [8.x] 6 consecutive failures in step release-tests
  • [8.x] 6 failures in test testGet (1.1% fail rate in 552 executions)
  • [8.x] 6 failures in step release-tests (100.0% fail rate in 6 executions)
  • [8.x] 6 failures in pipeline elasticsearch-periodic (46.2% fail rate in 13 executions)

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

@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 failures in test testGet (0.3% fail rate in 597 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 Oct 4, 2024
@elasticsearchmachine
Copy link
Collaborator Author

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

matthewabbott pushed a commit to matthewabbott/elasticsearch that referenced this issue Oct 10, 2024
@martijnvg
Copy link
Member

@davidkyle davidkyle 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 Nov 4, 2024
@dan-rubinstein
Copy link
Member

dan-rubinstein commented Nov 12, 2024

Looks like testGet was updated to testCRUD in this change. Looking back at the assertion that was failing, it looks related to the total number of endpoints we expect to exist (see here). testCRUD is not muted and has not been failing so it seems the updates we've made should have accounted for this. I'll go ahead and remove this from the muted tests.

@dan-rubinstein
Copy link
Member

Removed from muted tests in main. Looks like this is not muted in 8.x. Closing now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low-risk An open issue or test failure that is a low risk to future releases :ml Machine learning Team:ML Meta label for the ML team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

4 participants