✨ Add run_until_done scheduling algorithm
#121
kammceci.yml
on: pull_request
🧹 Lint
34s
🔎 Package Validation
/
...
/
🐉 LLVM 🐧 Linux x86_64
1m 6s
🔎 Package Validation
/
...
/
🐉 LLVM 🐧 Linux ARM64
1m 5s
🔎 Package Validation
/
...
/
🐉 LLVM 🍎 Mac ARM64
1m 10s
🔎 Package Validation
/
🐉 LLVM Arm Cortex M
1m 6s
🔎 Package Validation
/
🦌 GCC Arm Cortex M
0s
Matrix: ✅ Testing w/ Clang-Tidy enabled / run_tests
Annotations
19 errors and 7 warnings
|
🧹 Lint
Process completed with exit code 1.
|
|
🔎 Package Validation / linux_armv8_llvm / 🐉 LLVM 🐧 Linux ARM64
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
🔎 Package Validation / linux_armv8_llvm / 🐉 LLVM 🐧 Linux ARM64
The operation was canceled.
|
|
✅ Testing w/ Clang-Tidy enabled / run_tests (ubuntu-24.04, x86_64, Linux)
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ Testing w/ Clang-Tidy enabled / run_tests (ubuntu-24.04, x86_64, Linux)
The operation was canceled.
|
|
✅ Testing w/ Clang-Tidy enabled / run_tests (macos-latest, armv8, Macos)
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ Testing w/ Clang-Tidy enabled / run_tests (macos-latest, armv8, Macos)
The operation was canceled.
|
|
🔎 Package Validation / 🐉 LLVM Arm Cortex M
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
🔎 Package Validation / 🐉 LLVM Arm Cortex M
The operation was canceled.
|
|
🔎 Package Validation / linux_x86_64_llvm / 🐉 LLVM 🐧 Linux x86_64
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
🔎 Package Validation / linux_x86_64_llvm / 🐉 LLVM 🐧 Linux x86_64
The operation was canceled.
|
|
🔎 Package Validation / mac_os_x_latest_llvm / 🐉 LLVM 🍎 Mac ARM64
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
🔎 Package Validation / mac_os_x_latest_llvm / 🐉 LLVM 🍎 Mac ARM64
The operation was canceled.
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
✅ CI
Canceling since a higher priority waiting request for ✅ CI-refs/pull/83/merge exists
|
|
🧹 Lint
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/setup-python@v5. 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/
|
|
🔎 Package Validation / 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/
|
|
✅ Testing w/ Clang-Tidy enabled / 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/
|
|
✅ Testing w/ Clang-Tidy enabled / 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/
|
|
🔎 Package Validation / 🐉 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/
|
|
🔎 Package Validation / 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/
|
|
🔎 Package Validation / 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/
|