Skip to content

Draft - Add clang-tidy support in GHA #334

Draft - Add clang-tidy support in GHA

Draft - Add clang-tidy support in GHA #334

Triggered via pull request April 9, 2026 02:46
Status Success
Total duration 51m 3s
Artifacts 4

builds.yml

on: pull_request
Matrix: build
Build (docker-linux-arm64)
37m 49s
Build (docker-linux-arm64)
Build (docker-linux-x64)
46m 52s
Build (docker-linux-x64)
Build (cpp-example-collection-linux-arm64)
5m 16s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
4m 6s
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
examples/common/sdl_media.cpp:86:33 [bugprone-narrowing-conversions]: examples/common/sdl_media.cpp#L86
narrowing conversion from 'unsigned long' to signed type 'int' is implementation-defined
examples/common/sdl_media.cpp:69:31 [bugprone-narrowing-conversions]: examples/common/sdl_media.cpp#L69
narrowing conversion from '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:b5e8006831900f32f9d765ab0aebe20d738bf264cf09d20682359869c93b3b15
livekit-cpp-sdk-docker-arm64 Expired
2.69 GB
sha256:b4d83f62672b63705c65af6153a77ac7da140ab445d7772dae4d9cbf7c90a5d8
livekit-cpp-sdk-docker-x64 Expired
2.79 GB
sha256:b1f2476bc4ce0e5110f3983626da4a67dd6f8f5d9c32276d9013225c20d51da5
livekit-sdk-linux-x64 Expired
41.6 MB
sha256:24329d4eb486d78a08897af0f9b1d0cbe53aadb92dfa578c70cfc6810434d586