Skip to content

✅ CI

✅ CI #74

Triggered via schedule March 22, 2026 12:24
Status Failure
Total duration 6m 17s
Artifacts

ci.yml

on: schedule
library_check_v4  /  ...  /  lint
27s
library_check_v4 / lint / lint
library_check_v4  /  ...  /  docs
13s
library_check_v4 / docs / docs
deploy_check_v4  /  deploy
6m 7s
deploy_check_v4 / deploy
deploy_v5_check  /  ...  /  🐉 LLVM 🐧 Linux x86_64
5m 45s
deploy_v5_check / linux_x86_64_llvm / 🐉 LLVM 🐧 Linux x86_64
deploy_v5_check  /  ...  /  🐉 LLVM 🐧 Linux ARM64
5m 38s
deploy_v5_check / linux_armv8_llvm / 🐉 LLVM 🐧 Linux ARM64
deploy_v5_check  /  ...  /  🐉 LLVM 🍎 Mac ARM64
4m 10s
deploy_v5_check / mac_os_x_latest_llvm / 🐉 LLVM 🍎 Mac ARM64
deploy_v5_check  /  🐉 LLVM Arm Cortex M
2m 2s
deploy_v5_check / 🐉 LLVM Arm Cortex M
deploy_v5_check  /  🦌 GCC Arm Cortex M
0s
deploy_v5_check / 🦌 GCC Arm Cortex M
library_check_v5  /  ...  /  docs
library_check_v5 / docs / docs
library_check_v5  /  ...  /  lint
library_check_v5 / lint / lint
Matrix: library_check_v4 / tests / run_tests
Matrix: library_check_v5 / tests / run_tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 9 warnings
deploy_v5_check / 🐉 LLVM Arm Cortex M
Process completed with exit code 1.
deploy_v5_check / mac_os_x_latest_llvm / 🐉 LLVM 🍎 Mac ARM64
Process completed with exit code 1.
deploy_v5_check / linux_armv8_llvm / 🐉 LLVM 🐧 Linux ARM64
Process completed with exit code 1.
deploy_v5_check / linux_x86_64_llvm / 🐉 LLVM 🐧 Linux x86_64
Process completed with exit code 1.
library_check_v4 / docs / docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
library_check_v4 / lint / lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
deploy_v5_check / 🐉 LLVM Arm Cortex M
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
library_check_v4 / tests / run_tests (macos-latest, armv8, Macos)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
deploy_v5_check / mac_os_x_latest_llvm / 🐉 LLVM 🍎 Mac ARM64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
deploy_v5_check / linux_armv8_llvm / 🐉 LLVM 🐧 Linux ARM64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
deploy_v5_check / linux_x86_64_llvm / 🐉 LLVM 🐧 Linux x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
deploy_check_v4 / deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/
library_check_v4 / tests / run_tests (ubuntu-24.04, x86_64, Linux)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1. 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/