added a utility library for version and updated docs #650
frogrammer9build.yml
on: pull_request
build-gcc-and-test
48s
build-clang
44s
build-gcc-lto
28s
build-clang-lto
40s
build-clang-macos
1m 7s
build-clang-macos-lto
1m 9s
unit-tests
13s
Annotations
9 errors and 19 warnings
|
build-gcc-lto
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-clang-lto
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-clang
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-gcc-and-test
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-clang-macos
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-clang-macos
The operation was canceled.
|
|
build-clang-macos-lto
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
build-clang-macos-lto
The operation was canceled.
|
|
Build and Test
Canceling since a higher priority waiting request for Build and Test-refs/pull/108/merge exists
|
|
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/
|
|
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-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
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#L49
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L38
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L35
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L33
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L29
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
build-clang:
src/example_dtree/entry.c#L26
Value stored to 'error' is never read [clang-analyzer-deadcode.DeadStores]
|
|
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/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-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-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 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-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 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
|
212 KB |
sha256:fc952830d3c71aed3ec575a3ab565acdd08b9b327155b5ba48876895973282b6
|
|
|
build-artifacts-clang-lto
|
332 KB |
sha256:6a65fb6a6823db32c685b82b68377332a59053034f397618b6ebf220ed7a451f
|
|
|
build-artifacts-gcc
|
229 KB |
sha256:959a26833068ffcfb878c450b9fdb641f83002827df9b2e53fa1b644a76292fb
|
|
|
build-artifacts-gcc-lto
|
519 KB |
sha256:5b7b34388f12884f536cc2705bfc7ce9ff6669f4d3a69c6b4f90c6832c13b9ae
|
|