Skip to content

Events Being Dropped on Connection #669

Events Being Dropped on Connection

Events Being Dropped on Connection #669

Triggered via pull request May 13, 2026 20:08
Status Failure
Total duration 43m 7s
Artifacts 6

builds.yml

on: pull_request
Build (docker-linux-arm64)
25m 1s
Build (docker-linux-arm64)
Build (docker-linux-x64)
35m 13s
Build (docker-linux-x64)
License Check  /  License Check
4s
License Check / License Check
Pin Check  /  Pin Check
14s
Pin Check / Pin Check
clang-format
25s
clang-format
clang-tidy
11m 0s
clang-tidy
Matrix: build
Build (cpp-example-collection-linux-arm64)
5m 2s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
6m 42s
Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
Build (macos-arm64)
Process completed with exit code 1.
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:52322bcfb55e880e882f7b8c6081b80445683104a90b23b490be0bac549f6367
livekit-cpp-sdk-docker-x64 Expired
2.94 GB
sha256:683f15c6ed4d0dc2dfaf98f5986eaff68685506c06836c1765e1203447a21eb8
livekit-sdk-linux-arm64 Expired
23.2 MB
sha256:5cf7c2666bf466e3f7a0beb4d4ce2b406e57dabca3dfb43640eb7cfc208c561d
livekit-sdk-linux-x64 Expired
24.9 MB
sha256:3df2c362306ca9d5c55dcb33f6b62d95158f57028918285ff76cdb1c553c7a64
livekit-sdk-macos-x64 Expired
19.8 MB
sha256:f0de44ace2872dfd315f78a658a1898651857a0182c6ab592809040742ef3f24
livekit-sdk-windows-x64 Expired
11.4 MB
sha256:ea4ab6980fe7497769d75a3181aacd142946ad4326f05f42dfc4f8dbede28d6e