Skip to content

DP-2.2 QoS policer matching on next-hop-group #9724

DP-2.2 QoS policer matching on next-hop-group

DP-2.2 QoS policer matching on next-hop-group #9724

Triggered via pull request October 3, 2024 23:50
Status Success
Total duration 42s
Artifacts

protobufs.yml

on: pull_request
Validate Protobufs
33s
Validate Protobufs
Validate OpenConfig Paths
29s
Validate OpenConfig Paths
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Validate OpenConfig Paths
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Validate OpenConfig Paths
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Validate Protobufs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Validate Protobufs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v3, actions/cache@v3, arduino/setup-protoc@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/