Implement memory regions iterators #665
moojekbuild.yml
on: pull_request
build-gcc-and-test
39s
build-clang
1m 23s
build-gcc-lto
34s
build-clang-lto
42s
build-clang-macos
1m 6s
build-clang-macos-lto
1m 34s
unit-tests
7s
Annotations
27 warnings
|
unit-tests
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. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L240
‘nonnull’ argument ‘size_cellsOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L240
‘nonnull’ argument ‘address_cellsOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L227
‘nonnull’ argument ‘entryOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L204
‘nonnull’ argument ‘bufOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L141
‘nonnull’ argument ‘propOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L110
‘nonnull’ argument ‘nodeOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L93
‘nonnull’ argument ‘nodeOUT’ compared to NULL [-Wnonnull-compare]
|
|
unit-tests:
tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L81
‘nonnull’ argument ‘nodeOUT’ compared to NULL [-Wnonnull-compare]
|
|
build-gcc-lto
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-gcc-and-test
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-clang-lto
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-clang-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, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-clang-macos
cmake 4.3.2 is already installed and up-to-date.
To reinstall 4.3.2, run:
brew reinstall cmake
|
|
build-clang
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-clang:
src/example_dtree/entry.c#L21
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L19
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L17
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L340
do not use 'else' after 'return' [readability-else-after-return]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L257
do not use 'else' after 'return' [readability-else-after-return]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L89
statement should be inside braces [readability-braces-around-statements]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L87
statement should be inside braces [readability-braces-around-statements]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L9
invalid case style for global variable 'hal_riscv_fdt_initialized' [readability-identifier-naming]
|
|
build-clang:
src/kernel/hal/arch/riscv/memory_region.c#L8
invalid case style for global variable 'hal_riscv_fdt' [readability-identifier-naming]
|
|
build-clang:
src/kernel/memory_management/physical_memory/allocator.c#L149
redundant explicit casting to the same type 'uintptr_t' (aka 'unsigned long') as the sub-expression, remove this casting [readability-redundant-casting]
|
|
build-clang-macos-lto
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-clang-macos-lto
cmake 4.3.2 is already installed and up-to-date.
To reinstall 4.3.2, run:
brew reinstall cmake
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
build-artifacts-clang
|
221 KB |
sha256:cc4656f4fb18e3aeb99dd653f82ca1941459ff67e3c3deb0fa441582ecc5755b
|
|
|
build-artifacts-clang-lto
|
339 KB |
sha256:5d4868fcb536bab5e46763182ad3d9822acf3a187b14f42e7bb0613177bdec48
|
|
|
build-artifacts-clang-macos
|
216 KB |
sha256:8c57d852478744ec4699f5fe016a10a2a9d0bc72cdf28ac01a1a6b99d7f8be43
|
|
|
build-artifacts-clang-macos-lto
|
397 KB |
sha256:ff79522553e255c556373f30f1a8571479ce1a910ec1e4c640b2f6e3977c1bf7
|
|
|
build-artifacts-gcc
|
240 KB |
sha256:e16db09c1c9edbf56231f86eb0aa191ac0c778ed13e043249d1b51abd0a2c72a
|
|
|
build-artifacts-gcc-lto
|
543 KB |
sha256:b3f9427c2421b0e0190e931895abd1d8d7c59acd0b79d105de65f2ca064eb205
|
|