Skip to content

[CI] InferenceCrudIT testGetServicesWithCompletionTaskType failing #119959

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 Jan 10, 2025 · 5 comments · Fixed by #119982 or #121461
Closed

[CI] InferenceCrudIT testGetServicesWithCompletionTaskType failing #119959

elasticsearchmachine opened this issue Jan 10, 2025 · 5 comments · Fixed by #119982 or #121461
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 Jan 10, 2025

Build Scans:

Reproduction Line:

./gradlew ":x-pack:plugin:inference:qa:inference-service-tests:javaRestTest" --tests "org.elasticsearch.xpack.inference.InferenceCrudIT.testGetServicesWithCompletionTaskType" -Dtests.seed=BD2952ED26FBFFF5 -Dbuild.snapshot=false -Dtests.jvm.argline="-Dbuild.snapshot=false" -Dlicense.key=x-pack/license-tools/src/test/resources/public.key -Dtests.locale=lt-LT -Dtests.timezone=Africa/Maseru -Druntime.java=23

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: 
Expected: <10>
     but: was <9>

Issue Reasons:

  • [8.x] 4 failures in test testGetServicesWithCompletionTaskType (2.5% fail rate in 159 executions)
  • [8.x] 3 failures in step part-2 (8.6% fail rate in 35 executions)
  • [8.x] 3 failures in pipeline elasticsearch-pull-request (8.6% fail rate in 35 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 Jan 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch main

Mute Reasons:

  • [main] 2 consecutive failures in step release-tests
  • [main] 5 failures in test testGetServicesWithCompletionTaskType (1.3% fail rate in 395 executions)
  • [main] 2 failures in step release-tests (66.7% fail rate in 3 executions)
  • [main] 3 failures in step part-2 (1.6% fail rate in 185 executions)
  • [main] 4 failures in pipeline elasticsearch-pull-request (2.2% fail rate in 186 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 Jan 10, 2025
@elasticsearchmachine
Copy link
Collaborator Author

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

@jonathan-buttner jonathan-buttner 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 Jan 15, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 4 failures in test testGetServicesWithCompletionTaskType (2.5% fail rate in 159 executions)
  • [8.x] 3 failures in step part-2 (8.6% fail rate in 35 executions)
  • [8.x] 3 failures in pipeline elasticsearch-pull-request (8.6% fail rate in 35 executions)

Build Scans:

@jonathan-buttner jonathan-buttner linked a pull request Jan 31, 2025 that will close this issue
@jonathan-buttner
Copy link
Contributor

PR: #121461

@jonathan-buttner
Copy link
Contributor

Fixed by the above PR

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
2 participants