-
Notifications
You must be signed in to change notification settings - Fork 19
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
[WIP] Kserve: RHOAI 2.18.0 RC performance gating #685
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Going ahead with a full test, as I believe all the key changes related to the OpenShift AI operator were already released in 2.17.0. So, I don't expect anything unexpected. /test jump-ci rhoai-4xh100 kserve vllm_cpt_single_model_gating |
🔴 Test of 'kserve test test_ci' failed after 06 hours 34 minutes 08 seconds. 🔴 • Link to the test results. • Link to the reports index. Test configuration:
|
… performance gating test for 2.18.0 RC1
Removed the Re-launching the kserve model-serving gating test to generate the plots and regression analysis report for the Prometheus data, which failed to generate previously due to some errors. /test jump-ci rhoai-4xh100 kserve vllm_cpt_single_model_gating |
🔴 Test of 'kserve test test_ci' failed after 06 hours 20 minutes 44 seconds. 🔴 • Link to the test results. • Link to the reports index. Test configuration:
|
@mcharanrm: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The email didn’t include a tag, so I used a custom tag with the valid SHA digest provided. Clients will always pull the image using the SHA digest. If a valid tag is given but the digest is invalid, clients won’t be able to download the image.
The SHA digest is only considered when both a tag and digest are provided.