fix: fix gyroscope range values #10
UncleRusbuild.yml
on: pull_request
build-examples
/
target
4s
Matrix: build-examples / build
build-examples
/
Final result of build matrix
2s
Annotations
72 errors and 18 warnings
|
build-examples / build (esp32c6, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c3, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c5, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c3, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c61, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c5, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c5, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c5, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c61, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c61, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c61, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c5, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s2, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32p4, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32p4, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s2, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32p4, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s2, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32p4, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32p4, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s2, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s2, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32h2, latest)
The operation was canceled.
|
|
build-examples / build (esp32c6, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c6, v5.2)
The operation was canceled.
|
|
build-examples / build (esp32c2, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c2, v5.2)
The operation was canceled.
|
|
build-examples / build (esp32c2, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c2, latest)
The operation was canceled.
|
|
build-examples / build (esp32, latest)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32, latest)
The operation was canceled.
|
|
build-examples / build (esp32c3, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c3, v5.5)
The operation was canceled.
|
|
build-examples / build (esp32c2, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c2, v5.5)
The operation was canceled.
|
|
build-examples / build (esp32c3, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c2, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c2, v5.4)
The operation was canceled.
|
|
build-examples / build (esp32c3, v5.2)
The operation was canceled.
|
|
build-examples / build (esp32, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32, v5.3)
The operation was canceled.
|
|
build-examples / build (esp32c6, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c6, v5.5)
The operation was canceled.
|
|
build-examples / build (esp32s3, v5.5)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, v5.5)
The operation was canceled.
|
|
build-examples / build (esp32, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32, v5.4)
The operation was canceled.
|
|
build-examples / build (esp32c3, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c3, v5.4)
The operation was canceled.
|
|
build-examples / build (esp32, v5.2)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32, v5.2)
The operation was canceled.
|
|
build-examples / build (esp32s3, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, v5.3)
The operation was canceled.
|
|
build-examples / build (esp32c2, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32s3, v5.4)
The operation was canceled.
|
|
build-examples / build (esp32c2, v5.3)
The operation was canceled.
|
|
build-examples / build (esp32c6, v5.4)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c6, v5.4)
The operation was canceled.
|
|
build-examples / build (esp32c6, v5.3)
The run was canceled by @UncleRus.
|
|
build-examples / build (esp32c6, v5.3)
The operation was canceled.
|
|
build-examples / Final result of build matrix
Process completed with exit code 1.
|
|
Build examples
The run was canceled by @UncleRus.
|
|
Build examples
The run was canceled by @UncleRus.
|
|
build-examples / target
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. 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-examples / build (esp32c2, v5.2)
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. 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-examples / build (esp32c2, latest)
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. 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-examples / build (esp32, latest)
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. 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-examples / build (esp32c3, v5.5)
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. 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-examples / build (esp32c2, v5.5)
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. 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-examples / build (esp32c3, v5.2)
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. 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-examples / build (esp32c2, v5.4)
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. 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-examples / build (esp32, v5.3)
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. 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-examples / build (esp32c6, v5.5)
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. 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-examples / build (esp32s3, v5.5)
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. 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-examples / build (esp32, v5.4)
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. 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-examples / build (esp32c3, v5.4)
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. 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-examples / build (esp32, v5.2)
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. 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-examples / build (esp32s3, v5.3)
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. 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-examples / build (esp32c2, v5.3)
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. 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-examples / build (esp32c6, v5.4)
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. 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-examples / build (esp32c6, v5.3)
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. 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/
|