doc: fix latex #1150
ci-linux-ros.yml
on: pull_request
Matrix: CI
check-ci-linux-ros
4s
Annotations
16 errors and 6 warnings
|
Jazzy / Release
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Rolling / Release / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Jazzy / Debug
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Jazzy / Debug
The operation was canceled.
|
|
Rolling / Debug / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Rolling / Debug / Vectorization
The operation was canceled.
|
|
Humble / Debug / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Humble / Debug / Vectorization
The operation was canceled.
|
|
Jazzy / Debug / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Jazzy / Debug / Vectorization
The operation was canceled.
|
|
Jazzy / Release / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Jazzy / Release / Vectorization
The operation was canceled.
|
|
Humble / Release / Vectorization
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Humble / Release / Vectorization
The operation was canceled.
|
|
check-ci-linux-ros
Process completed with exit code 1.
|
|
CI - Linux - ROS
Canceling since a higher priority waiting request for CI - Linux - ROS-refs/pull/453/merge exists
|
|
Jazzy / Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|
|
Rolling / Debug / Vectorization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|
|
Humble / Debug / Vectorization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|
|
Jazzy / Debug / Vectorization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|
|
Jazzy / Release / Vectorization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|
|
Humble / Release / Vectorization
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ros-industrial/industrial_ci@master. 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/
|