Bump FRR to 10.5.3 #1144
trigger.yml
on: pull_request
check-trigger
5s
build-aarch64
/
Build infix aarch64_minimal
19m 36s
build-arm
/
Build infix arm_minimal
18m 54s
test-publish-x86_64
/
Upload Latest Build
Annotations
10 errors and 4 warnings
|
build-x86_64 / Build infix x86_64_minimal
Canceling since a higher priority waiting request for ci-1451 exists
|
|
build-x86_64 / Build infix x86_64_minimal
The operation was canceled.
|
|
build-arm / Build infix arm_minimal
Canceling since a higher priority waiting request for ci-1451 exists
|
|
build-arm / Build infix arm_minimal
The operation was canceled.
|
|
build-aarch64 / Build infix aarch64_minimal
Canceling since a higher priority waiting request for ci-1451 exists
|
|
build-aarch64 / Build infix aarch64_minimal
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for ci-1451 exists
|
|
CI
Canceling since a higher priority waiting request for ci-1451 exists
|
|
CI
Canceling since a higher priority waiting request for ci-1451 exists
|
|
CI
Canceling since a higher priority waiting request for ci-1451 exists
|
|
unit-test / Build infix x86_64_minimal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-x86_64 / Build infix x86_64_minimal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-arm / Build infix arm_minimal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
build-aarch64 / Build infix aarch64_minimal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|