Skip to content

Implement memory regions iterators #671

Implement memory regions iterators

Implement memory regions iterators #671

Triggered via pull request June 7, 2026 20:32
Status Success
Total duration 1m 55s
Artifacts 6

build.yml

on: pull_request
build-gcc-and-test
50s
build-gcc-and-test
build-clang
55s
build-clang
build-gcc-lto
34s
build-gcc-lto
build-clang-lto
38s
build-clang-lto
build-clang-macos
1m 13s
build-clang-macos
build-clang-macos-lto
1m 50s
build-clang-macos-lto
unit-tests
19s
unit-tests
Fit to window
Zoom out
Zoom in

Annotations

18 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 16th, 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
comparison of nonnull parameter 'size_cellsOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L240
comparison of nonnull parameter 'address_cellsOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L227
comparison of nonnull parameter 'entryOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L204
comparison of nonnull parameter 'bufOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L141
comparison of nonnull parameter 'propOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L110
comparison of nonnull parameter 'nodeOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L93
comparison of nonnull parameter 'nodeOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-compare]
unit-tests: tests/kernel/memory_management/physical_memory/test_hal_memory_regions.c#L81
comparison of nonnull parameter 'nodeOUT' equal to a null pointer is 'false' on first encounter [-Wtautological-pointer-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 16th, 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 16th, 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 16th, 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
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 16th, 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/kernel/memory_management/physical_memory/allocator.c#L150
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
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 16th, 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-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 16th, 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
167 KB
sha256:0bcaf34ad3ef1a530d7b2c71bbd294c6870364d8d2ca45bb4e5a89bfa434ba69
build-artifacts-clang-lto
264 KB
sha256:5a0546cbad0f48807f1f759b00720a19702a8226a44e5147a833ddff20473ca7
build-artifacts-clang-macos
162 KB
sha256:c463c2dadb06ed0a9d5a41666c7365c20bed0daf3b32c86ebe6b8afa57360568
build-artifacts-clang-macos-lto
315 KB
sha256:0d8b7a0903016d76f7059c0d9338cb1b5fd4b9e96fa7fba5e2c8612d7e862557
build-artifacts-gcc
183 KB
sha256:9e0afda6899ad6c4fdb336870d490e16d73b90e8a74e856e2f40cef22e09e928
build-artifacts-gcc-lto
477 KB
sha256:ae496e38f7da8b5915ab45e0e0506849e2e6dfee5ef4b9dc3cc0acf416fe9f15