Skip to content

Adjust result.h error condition behavior #690

Adjust result.h error condition behavior

Adjust result.h error condition behavior #690

Triggered via pull request May 14, 2026 19:22
Status Failure
Total duration 34m 54s
Artifacts 7

builds.yml

on: pull_request
Build (docker-linux-arm64)
30m 37s
Build (docker-linux-arm64)
Build (docker-linux-x64)
30m 33s
Build (docker-linux-x64)
License Check  /  License Check
7s
License Check / License Check
Pin Check  /  Pin Check
11s
Pin Check / Pin Check
clang-format
15s
clang-format
clang-tidy
11m 16s
clang-tidy
Matrix: build
Build (cpp-example-collection-linux-arm64)
4m 9s
Build (cpp-example-collection-linux-arm64)
Build (cpp-example-collection-x64)
4m 2s
Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
Build (cpp-example-collection-x64)
Process completed with exit code 2.
Build (cpp-example-collection-linux-arm64)
Process completed with exit code 2.
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 (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 (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 (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:2ef96c982efe6916f0f5afbd7e9da9808b395e8eaad053268b0d5fc3a53d2717
livekit-cpp-sdk-docker-x64 Expired
2.94 GB
sha256:ad940714d9ee1155fbeb1019c2ffbab8c577a1ab55de1b10ac26678b0290498f
livekit-sdk-linux-arm64 Expired
23.2 MB
sha256:67464fda174f9b170be2d9a0446b3dbf52d4ab52c012963a2445aad984a33350
livekit-sdk-linux-x64 Expired
24.9 MB
sha256:6d7b6e6bb1abcae5fe7c37783170cdc71a8e1017e7cf8149f17d4edeeda1c0b2
livekit-sdk-macos-arm64 Expired
19 MB
sha256:e18631d3d535dd0e414f8117601e7b3aed67493fdb6683ae5bc4e19bf27f0777
livekit-sdk-macos-x64 Expired
19.8 MB
sha256:ce04c7c66d95120d67d81ef032f407cda95cfc27a158004d73c4acdbbdf0424f
livekit-sdk-windows-x64 Expired
11.4 MB
sha256:05d76ebec653a1510191f789952b513a70e844f4fa28ae40666bc278d80b9d8f