Skip to content

Unified CI workflow for smarter PR gating #26

Unified CI workflow for smarter PR gating

Unified CI workflow for smarter PR gating #26

Triggered via pull request June 3, 2026 14:25
Status Failure
Total duration 1h 50m 32s
Artifacts 12

ci.yml

on: pull_request
Detect Changes
6s
Detect Changes
License Check  /  License Check
7s
License Check / License Check
Pin Check  /  Pin Check
12s
Pin Check / Pin Check
Builds  /  Build (docker-linux-arm64)
27m 21s
Builds / Build (docker-linux-arm64)
Builds  /  Build (docker-linux-x64)
31m 55s
Builds / Build (docker-linux-x64)
Tests  /  Code Coverage
18m 2s
Tests / Code Coverage
Quality Checks  /  clang-format
20s
Quality Checks / clang-format
Quality Checks  /  clang-tidy
11m 9s
Quality Checks / clang-tidy
Generate Docs  /  Generate and verify docs
29s
Generate Docs / Generate and verify docs
Matrix: Builds / build
Matrix: Tests / test
Builds  /  Build (cpp-example-collection-linux-arm64)
8m 50s
Builds / Build (cpp-example-collection-linux-arm64)
Builds  /  Build (cpp-example-collection-x64)
6m 25s
Builds / Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

5 errors, 9 warnings, and 4 notices
Builds / Build (macos-x64)
The process '/usr/local/bin/git' failed with exit code 128
Builds / Build (macos-x64)
Failed to recurse into submodule path 'client-sdk-rust'
Builds / Build (macos-x64)
Fetched in submodule path 'client-sdk-rust/yuv-sys/libyuv', but it did not contain 917276084a49be726c90292ff0a6b0a3d571a6af. Direct fetching of that commit failed.
Builds / Build (macos-x64)
unable to access 'https://chromium.googlesource.com/libyuv/libyuv/': Failed to connect to chromium.googlesource.com port 443 after 5 ms: Couldn't connect to server
Tests / Test (macos-x64)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Builds / Build (macos-arm64)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Tests / Code Coverage
(WARNING) /home/runner/work/client-sdk-cpp/client-sdk-cpp/src/logging.cpp:53: Ignoring negative hits in: branch 7 taken -1.
Tests / Code Coverage
(WARNING) /home/runner/work/client-sdk-cpp/client-sdk-cpp/src/logging.cpp:33: Ignoring negative hits in: branch 7 taken -12.
Builds / 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...
Builds / Build (cpp-example-collection-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...
Tests / Test (macos-arm64)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Tests / Test (macos-arm64)
The following taps are not trusted: aws/tap azure/bicep hashicorp/tap Homebrew will ignore formulae, casks and commands from these taps when `HOMEBREW_REQUIRE_TAP_TRUST` is set. This will become the default in Homebrew 6.0.0 or 5.2.0, whichever comes first. Enable trust checks now with: export HOMEBREW_REQUIRE_TAP_TRUST=1 Trust specific formulae, casks or commands with: brew trust --formula <user>/<tap>/<formula> brew trust --cask <user>/<tap>/<cask> brew trust --command <user>/<tap>/<command> or trust installed formulae from these taps with: brew trust --formula azure/bicep/bicep brew trust --formula hashicorp/tap/packer You can trust all formulae, casks and commands from these taps with: brew trust aws/tap azure/bicep hashicorp/tap Prefer trusting only the specific formulae, casks or commands you need. Untap them with: brew untap aws/tap azure/bicep hashicorp/tap To keep allowing them by default during the transition: export HOMEBREW_NO_REQUIRE_TAP_TRUST=1 This is not recommended and will be removed in a later release.
Builds / 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 16th, 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/
Tests / Test (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 16th, 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/
sccache stats - build
0% - 0 hits, 0 misses, 0 errors
Builds / Build (windows-x64)
sccache enabled (RUSTC_WRAPPER=sccache)
sccache stats - test
0% - 0 hits, 0 misses, 0 errors
Tests / Test (windows-x64)
sccache enabled (RUSTC_WRAPPER=sccache)

Artifacts

Produced during runtime
Name Size Digest
coverage-report
516 KB
sha256:c81d28647829171ab3d95bd80d8a7ad3239e6b856ff4a335fe0e78655ed95ff0
livekit-cpp-docs
2.54 MB
sha256:9dcec75be4815c8bb7c88223a7207d1ab181f90fcbcb8df1c888db5bf2e30c6e
livekit-cpp-sdk-docker-arm64
2.84 GB
sha256:cb72d668df3f7d72232fa8c2625eba78da5f99a705ff6fe429a86a695a3ae197
livekit-cpp-sdk-docker-x64
2.94 GB
sha256:8e5afabf5dba0b1ff747da4a4a608ce00abe219b1632076bd3701dc3e1c3dd42
livekit-sdk-linux-arm64
23.2 MB
sha256:1856f4d99fc8a47c8f17855bffd7013c6e8f2ae3424016072de35ae27e8a8a73
livekit-sdk-linux-x64
24.9 MB
sha256:88486766ded863dc766610c029ec97ff9556af009a797db02507f2b5da86be26
livekit-sdk-macos-arm64
19 MB
sha256:8b6052b1101d2df8952d053e7e9a53fa397f11b2202daf8f23edb3e8eed0925f
livekit-sdk-windows-x64
11.3 MB
sha256:4688ac708dddf05751c925f8f48d85aa53bd7bf80648bac620f1f298254535b1
test-results-linux-arm64
1.47 MB
sha256:0142db7bc735cada5606b1773823a76f52c7733c253364fbe0b82bcbbeb635f2
test-results-linux-x64
1.5 MB
sha256:e6ae1fcd5c2ccc2aa1f03b56cc0a13ebb9301571420c3e661672fc94e33f418b
test-results-macos-arm64
20.4 MB
sha256:44a95b4edd826281de8079b4a58d050fa0a9498e33ce8c40cc0dc820e2b5ea8c
test-results-windows-x64
6 KB
sha256:3d982a513466e2117df40785e595b40d8b56b242fcb70d64e22e02d9dde2b47c