Skip to content

FFI panic event support #41

FFI panic event support

FFI panic event support #41

Triggered via pull request June 4, 2026 01:17
Status Success
Total duration 36m 3s
Artifacts 14

ci.yml

on: pull_request
Detect Changes
7s
Detect Changes
License Check  /  License Check
7s
License Check / License Check
Matrix: Builds / build
Matrix: Tests / test
Builds  /  Build (docker-linux-arm64)
23m 17s
Builds / Build (docker-linux-arm64)
Builds  /  Build (docker-linux-x64)
30m 12s
Builds / Build (docker-linux-x64)
Tests  /  Code Coverage
15m 58s
Tests / Code Coverage
C++ Checks  /  clang-format
22s
C++ Checks / clang-format
C++ Checks  /  clang-tidy
11m 31s
C++ Checks / clang-tidy
Generate Docs  /  Generate and verify docs
29s
Generate Docs / Generate and verify docs
Builds  /  Build (cpp-example-collection-linux-arm64)
5m 49s
Builds / Build (cpp-example-collection-linux-arm64)
Builds  /  Build (cpp-example-collection-x64)
5m 31s
Builds / Build (cpp-example-collection-x64)
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
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 / 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/
Builds / Build (macos-x64)
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-x64)
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-x64)
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 -5.
Tests / Code Coverage
(WARNING) /home/runner/work/client-sdk-cpp/client-sdk-cpp/src/logging.cpp:33: Ignoring negative hits in: branch 7 taken -11.
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...
CI
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: suzuki-shunsuke/required-status-check-action@2b5a46064846b09381852c2c4217e898f639e768. 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-report
516 KB
sha256:c0758d82548ac7ebbfd2f025e1c62e626de53ec2980a0bfe313be750c31e0e8e
livekit-cpp-docs
2.54 MB
sha256:9e7515c1e2c487ffd5ec667d32e0df64aaf6cfd27e3c6e40eed4337abbe83afb
livekit-cpp-sdk-docker-arm64
2.92 GB
sha256:5548ca8cad5b7d8b4286a057d1f8378d74e3b6ad499aa089303c6c3adde11e61
livekit-cpp-sdk-docker-x64
3.05 GB
sha256:95c387e835e7c410aced0fd77857268f23e62210e29fe517fbdc611437f7540e
livekit-sdk-linux-arm64
23.1 MB
sha256:da7649cb1fcce95941555f55451a39498594d8f89f3b6c58336b44185a9ba1b4
livekit-sdk-linux-x64
24.7 MB
sha256:1a3a91313cd7aebb06928b0b54f76fc825694b05ac52bce69ed3f532dec7c3ad
livekit-sdk-macos-arm64
18.9 MB
sha256:783279ff8f7c075ff40eeb0936501cf11364a270180eb738e8fd3aaa54e6437a
livekit-sdk-macos-x64
19.8 MB
sha256:5297df31ce543ecd849586fd6f37f61c5c3f9fb62d8386476670fdfab95e60e8
livekit-sdk-windows-x64
11.3 MB
sha256:0fe8e73b68665a8994a70d46fabb5ce1416c2749396b79b0b7f4d40fe15fa1de
test-results-linux-arm64
1.44 MB
sha256:c8386397ff3522b3437e3f4713078767603ee504892c1e09e7825b6e83f1858b
test-results-linux-x64
1.46 MB
sha256:fdd11d0cbf10b6c494003bc3e98575ff45e6746d32b8e75d64438aa416dea43a
test-results-macos-arm64
1.38 MB
sha256:0f699b6d1133b2584669ab0493c8597f0e5bcfa16acd7df4ebbd6aeee3f18654
test-results-macos-x64
1.64 MB
sha256:a5ff7ee20c0cad0a685001c7c81de1694057f4542ab726eacd6032a84863d0c7
test-results-windows-x64
6 KB
sha256:067ad9c87f351e14e05284af420c99bcb6aad7140d9e0ea77a0b1cb40ee022af