Skip to content

Draft - Add clang-tidy support in GHA #355

Draft - Add clang-tidy support in GHA

Draft - Add clang-tidy support in GHA #355

Triggered via pull request April 9, 2026 22:07
Status Failure
Total duration 49m 38s
Artifacts 4

builds.yml

on: pull_request
Matrix: build
Build (docker-linux-arm64)
38m 0s
Build (docker-linux-arm64)
Build (docker-linux-x64)
44m 36s
Build (docker-linux-x64)
Build (cpp-example-collection-linux-arm64)
4m 6s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
4m 54s
Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 16 warnings
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
src/room_proto_converter.cpp:403:13 [bugprone-narrowing-conversions]: src/room_proto_converter.cpp#L403
narrowing conversion from '::uint32_t' (aka 'unsigned int') to signed type 'int' is implementation-defined
src/video_stream.cpp:105:42 [bugprone-narrowing-conversions]: src/video_stream.cpp#L105
narrowing conversion from 'std::int64_t' (aka 'long') to signed type 'ListenerId' (aka 'int') is implementation-defined
Build (cpp-example-collection-linux-arm64)
Process completed with exit code 1.
Build (cpp-example-collection-x64)
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/
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
bridge/include/livekit_bridge/rpc_constants.h:34:12 [performance-enum-size]: bridge/include/livekit_bridge/rpc_constants.h#L34
enum 'Action' 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/track.h:54:12 [performance-enum-size]: include/livekit/track.h#L54
enum 'AudioTrackFeature' 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/track.h:48:12 [performance-enum-size]: include/livekit/track.h#L48
enum 'StreamState' 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/track.h:40:12 [performance-enum-size]: include/livekit/track.h#L40
enum 'TrackSource' 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/track.h:34:12 [performance-enum-size]: include/livekit/track.h#L34
enum 'TrackKind' 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/video_frame.h:27:12 [performance-enum-size]: include/livekit/video_frame.h#L27
enum 'VideoBufferType' 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/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
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:b79314ce15dd3818c80e11c28c0f897ef36242443bfb66eb7655e12b75c0dbfa
livekit-cpp-sdk-docker-arm64 Expired
2.69 GB
sha256:391e9940a443640fdd3f0f36a51870face36e05ccc902c595b43bc191d3a0d00
livekit-cpp-sdk-docker-x64 Expired
2.79 GB
sha256:d28e6431641b23ab5f41016145cfe57e138faed29577c1bd1714fcd345be6e99
livekit-sdk-linux-x64 Expired
41.6 MB
sha256:b03287cbf17ed9989848ec15c42d110dc2243ebe6f80f4f6e79b6d34a8981a8e