Skip to content

Draft - Add clang-tidy support in GHA #335

Draft - Add clang-tidy support in GHA

Draft - Add clang-tidy support in GHA #335

Triggered via pull request April 9, 2026 03:27
Status Success
Total duration 51m 37s
Artifacts 4

builds.yml

on: pull_request
Matrix: build
Build (docker-linux-arm64)
36m 46s
Build (docker-linux-arm64)
Build (docker-linux-x64)
47m 24s
Build (docker-linux-x64)
Build (cpp-example-collection-linux-arm64)
5m 28s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
4m 7s
Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 16 warnings
src/tests/integration/test_audio_processing_module.cpp:899:22 [bugprone-narrowing-conversions]: src/tests/integration/test_audio_processing_module.cpp#L899
narrowing conversion from 'unsigned int' to signed type 'std::mt19937' (aka 'int') is implementation-defined
src/tests/integration/test_audio_processing_module.cpp:69:59 [bugprone-narrowing-conversions]: src/tests/integration/test_audio_processing_module.cpp#L69
narrowing conversion from 'unsigned int' to signed type 'std::mt19937' (aka 'int') is implementation-defined
src/tests/integration/test_audio_processing_module.cpp:69:34 [bugprone-narrowing-conversions]: src/tests/integration/test_audio_processing_module.cpp#L69
narrowing conversion from 'result_type' (aka 'unsigned int') to signed type 'std::mt19937' (aka 'int') is implementation-defined
src/data_track_stream.cpp:84:42 [bugprone-narrowing-conversions]: src/data_track_stream.cpp#L84
narrowing conversion from 'std::int64_t' (aka 'long') to signed type 'ListenerId' (aka 'int') is implementation-defined
src/audio_stream.cpp:127:42 [bugprone-narrowing-conversions]: src/audio_stream.cpp#L127
narrowing conversion from 'std::int64_t' (aka 'long') to signed type 'ListenerId' (aka 'int') is implementation-defined
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/
bridge/src/bridge_audio_track.cpp:65:34 [bugprone-easily-swappable-parameters]: bridge/src/bridge_audio_track.cpp#L65
2 adjacent parameters of 'pushFrame' of similar type ('int') are easily swapped by mistake
bridge/src/bridge_audio_track.cpp:46:34 [bugprone-easily-swappable-parameters]: bridge/src/bridge_audio_track.cpp#L46
2 adjacent parameters of 'pushFrame' of similar type ('int') are easily swapped by mistake
bridge/src/bridge_audio_track.cpp:33:23 [bugprone-easily-swappable-parameters]: bridge/src/bridge_audio_track.cpp#L33
2 adjacent parameters of 'BridgeAudioTrack' of similar type ('int') are easily swapped by mistake
include/livekit/logging.h:25:12 [performance-enum-size]: include/livekit/logging.h#L25
enum 'LogLevel' uses a larger base type ('int', size: 4 bytes) than necessary for its value set, consider using 'std::uint8_t' (1 byte) as the base type to reduce its size
include/livekit/local_data_track.h:101:3 [modernize-use-nodiscard]: include/livekit/local_data_track.h#L101
function 'ffi_handle_id' should be marked [[nodiscard]]
include/livekit/local_data_track.h:87:3 [modernize-use-nodiscard]: include/livekit/local_data_track.h#L87
function 'isPublished' should be marked [[nodiscard]]
examples/bridge_human_robot/human.cpp:359:25 [bugprone-implicit-widening-of-multiplication-result]: examples/bridge_human_robot/human.cpp#L359
result of multiplication in type 'int' is used as a pointer offset after an implicit widening conversion to type 'ptrdiff_t'
examples/bridge_human_robot/human.cpp:74:12 [performance-enum-size]: examples/bridge_human_robot/human.cpp#L74
enum 'SelectedSource' uses a larger base type ('int', size: 4 bytes) than necessary for its value set, consider using 'std::uint8_t' (1 byte) as the base type to reduce its size
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:344bd133804ea828cb65be42547000a8b458c0cb2d66fff658b312d04b46bf10
livekit-cpp-sdk-docker-arm64 Expired
2.69 GB
sha256:4017e105a55b1f34d214cf137ee80debb189dd88eb73d899bb93b69813a00b91
livekit-cpp-sdk-docker-x64 Expired
2.79 GB
sha256:630f2128e8cd0cf232e04d2117d34dcd739b395c30aa23c1691a3b66adf8c6db
livekit-sdk-linux-x64 Expired
41.6 MB
sha256:915653144c2aa594a2496f5d025f3c6c6d889db37ffb3fb2185734ee0419b933