Skip to content

[Backport 2.17] fix model stuck in deploying state during node crash/cluster restart #2834

[Backport 2.17] fix model stuck in deploying state during node crash/cluster restart

[Backport 2.17] fix model stuck in deploying state during node crash/cluster restart #2834

Re-run triggered October 22, 2024 22:55
Status Success
Total duration 6m 43s
Artifacts

test_bwc.yml

on: pull_request
Matrix: Test MLCommons BWC
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Test MLCommons BWC (17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test MLCommons BWC (17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test MLCommons BWC (11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Test MLCommons BWC (11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/