Skip to content

Fix/guard connection state #630

Fix/guard connection state

Fix/guard connection state #630

Triggered via pull request May 12, 2026 18:07
Status Failure
Total duration 37m 40s
Artifacts 7

builds.yml

on: pull_request
Build (docker-linux-arm64)
27m 23s
Build (docker-linux-arm64)
Build (docker-linux-x64)
33m 22s
Build (docker-linux-x64)
License Check  /  License Check
6s
License Check / License Check
Pin Check  /  Pin Check
15s
Pin Check / Pin Check
clang-format
43s
clang-format
clang-tidy
15m 10s
clang-tidy
Matrix: build
Build (cpp-example-collection-linux-arm64)
6m 40s
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

2 errors and 6 warnings
clang-format
Process completed with exit code 1.
clang-format: src/trace/trace_event.h#L713
code should be clang-formatted
Build (macos-arm64)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build (macos-arm64)
cmake 4.3.2 is already installed and up-to-date. To reinstall 4.3.2, run: brew reinstall cmake
Build (docker-linux-arm64)
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
Build (macos-x64)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
Build (macos-x64)
cmake 4.3.2 is already installed and up-to-date. To reinstall 4.3.2, run: brew reinstall cmake
Build (windows-x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: lukka/run-vcpkg@6fe69898af670ac05f4a8427cc5cff4fb361cee5. 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
livekit-cpp-sdk-docker-arm64 Expired
2.84 GB
sha256:fdcfb5cd6a6518060938a12e02d8fa4448c4853df60f1dc7745aa9b215edc655
livekit-cpp-sdk-docker-x64 Expired
2.94 GB
sha256:efbef1a70500e81eac9bdab0f307dad66bfcbad93318aa4fb2c7d2b475344acc
livekit-sdk-linux-arm64 Expired
23.2 MB
sha256:775ecab020e4d0f34db0940e0ca64cb2ab12691a1da4b5e10313f72e57ea7a20
livekit-sdk-linux-x64 Expired
24.9 MB
sha256:9e835333ccf85998c5ff2718e8ad9a1637e2052562fbbcc134ed054a2e67a300
livekit-sdk-macos-arm64 Expired
19.1 MB
sha256:80c748283bdfec31a5524b1f6619f9af0f594a80c221b5b5e91c24e052c73267
livekit-sdk-macos-x64 Expired
19.8 MB
sha256:6419a5e5d356fefd02457d9a90573c9a8257686b3f0fb9b096e915ca272b8ec1
livekit-sdk-windows-x64 Expired
11.4 MB
sha256:95ab84574592599643408ae4303902dc5979c7640da42f16c596736d9da0bbc2