Skip to content

Draft - Add clang-tidy support in GHA #331

Draft - Add clang-tidy support in GHA

Draft - Add clang-tidy support in GHA #331

Triggered via pull request April 8, 2026 23:40
Status Success
Total duration 51m 23s
Artifacts 4

builds.yml

on: pull_request
Matrix: build
Build (docker-linux-arm64)
36m 44s
Build (docker-linux-arm64)
Build (docker-linux-x64)
47m 21s
Build (docker-linux-x64)
Build (cpp-example-collection-linux-arm64)
6m 5s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
3m 56s
Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 17 warnings
clang-tidy
Process completed with exit code 1.
Build (linux-x64)
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/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/
clang-tidy
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/download-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/
clang-tidy
clang-tidy found 396 issue(s), threshold is 0
src/track_proto_converter.cpp:88:3 [bugprone-branch-clone]: src/track_proto_converter.cpp#L88
switch has 2 consecutive identical branches
src/track_proto_converter.cpp:71:3 [bugprone-branch-clone]: src/track_proto_converter.cpp#L71
switch has 2 consecutive identical branches
src/track_proto_converter.cpp:58:3 [bugprone-branch-clone]: src/track_proto_converter.cpp#L58
switch has 2 consecutive identical branches
src/ffi_client.cpp:726:7 [bugprone-empty-catch]: src/ffi_client.cpp#L726
empty catch statements hide issues; to handle exceptions appropriately, consider re-throwing, handling, or avoiding catch altogether
src/ffi_client.cpp:683:7 [bugprone-empty-catch]: src/ffi_client.cpp#L683
empty catch statements hide issues; to handle exceptions appropriately, consider re-throwing, handling, or avoiding catch altogether
src/ffi_client.cpp:654:36 [performance-unnecessary-copy-initialization]: src/ffi_client.cpp#L654
the variable 'track' is copy-constructed from a const reference but is never used; consider removing the statement
src/ffi_client.cpp:247:29 [bugprone-narrowing-conversions]: src/ffi_client.cpp#L247
narrowing conversion from 'size_t' (aka 'unsigned long') to signed type 'int' is implementation-defined
Build (docker-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, actions/upload-artifact@v4, docker/setup-buildx-action@v3. 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 (cpp-example-collection-linux-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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 (docker-linux-x64)
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, docker/setup-buildx-action@v3. 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 (cpp-example-collection-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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/

Artifacts

Produced during runtime
Name Size Digest
compile-database Expired
859 KB
sha256:bba19e54dd76197e980951e80d9a32dab498e38c5bc825e36b2d53628dabb190
livekit-cpp-sdk-docker-arm64 Expired
2.69 GB
sha256:2268f0bbc83c4251fb31738afefd1d5f1c10ceefd8d66d4537e7c162f0fed43e
livekit-cpp-sdk-docker-x64 Expired
2.79 GB
sha256:9dfa936e7d721e880ff903db7d6f06c14627bb2ca4d052e12c31fffb70fd786b
livekit-sdk-linux-x64 Expired
41.6 MB
sha256:7da0539283fa2f76fcd2fa5f572043905ffc42f383b80250f7aaa415c6f4a1fd