Skip to content
Build and Test ml-commons

Introduce gRPC streaming support for ML prediction and agent execution #13540

Sign in to view logs

Introduce gRPC streaming support for ML prediction and agent execution

Introduce gRPC streaming support for ML prediction and agent execution #13540

  • ml-commons-cicd-env-require-approval require an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by nathaliellenaa in Build and Test ml-commons #13540

Triggered via pull request April 15, 2026 00:06
@nathaliellenaanathaliellenaa
synchronize #4790
Status Waiting
Total duration –
Artifacts –
  • ml-commons-cicd-env-require-approval require an approval to start deploying changes

    View pending deployments

    View pending deployments
    requested by nathaliellenaa in Build and Test ml-commons #13540

CI-workflow.yml

on: pull_request_target
Get-Require-Approval  /  Require-Approval
12s
Get-Require-Approval / Require-Approval
spotless
1m 39s
spotless
Get-CI-Image-Tag  /  Get-CI-Image-Tag
6s
Get-CI-Image-Tag / Get-CI-Image-Tag
Matrix: Build and Test MLCommons Plugin on Windows
Matrix: Build and Test MLCommons Plugin on linux
Matrix: Test MLCommons Plugin on linux docker
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Deployment protection rules

Reviewers, timers, and other rules protecting deployments in this run
Event Environments Comment
@nathaliellenaa
nathaliellenaa
requested review
ml-commons-cicd-env-require-approval and
ml-commons-cicd-env-require-approval, ml-commons-cicd-env-require-approval, ml-commons-cicd-env-require-approval, and ml-commons-cicd-env-require-approval
-

Annotations

3 warnings
Get-CI-Image-Tag / Get-CI-Image-Tag
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Get-Require-Approval / Require-Approval
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
spotless
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
⚡