Skip to content

feat: add support for SimulateScenario #1581

feat: add support for SimulateScenario

feat: add support for SimulateScenario #1581

Triggered via pull request May 10, 2026 06:36
Status Failure
Total duration 54s
Artifacts

ci.yml

on: pull_request
Formatting
25s
Formatting
REUSE-3.2
12s
REUSE-3.2
Build and release
0s
Build and release
Matrix: Test
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 5 warnings
Formatting
Process completed with exit code 1.
Test (24)
Process completed with exit code 1.
src/tests/e2e.test.ts > livekit-rtc e2e > full reconnect fires Reconnected once and ends with one publication: packages/livekit-rtc/src/tests/e2e.test.ts#L857
AssertionError: expected +0 to be 1 // Object.is equality - Expected + Received - 1 + 0 ❯ src/tests/e2e.test.ts:857:34
src/tests/e2e.test.ts > livekit-rtc e2e > resume preserves the agent publication and does not fire Reconnected: packages/livekit-rtc/src/tests/e2e.test.ts#L777
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/tests/e2e.test.ts:777:34
Test (22)
The strategy configuration was canceled because "test._24" failed
Test (22)
The operation was canceled.
src/tests/e2e.test.ts > livekit-rtc e2e > full reconnect fires Reconnected once and ends with one publication: packages/livekit-rtc/src/tests/e2e.test.ts#L857
AssertionError: expected +0 to be 1 // Object.is equality - Expected + Received - 1 + 0 ❯ src/tests/e2e.test.ts:857:34
src/tests/e2e.test.ts > livekit-rtc e2e > resume preserves the agent publication and does not fire Reconnected: packages/livekit-rtc/src/tests/e2e.test.ts#L777
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/tests/e2e.test.ts:777:34
Test (20)
The strategy configuration was canceled because "test._24" failed
Test (20)
The operation was canceled.
src/tests/e2e.test.ts > livekit-rtc e2e > full reconnect fires Reconnected once and ends with one publication: packages/livekit-rtc/src/tests/e2e.test.ts#L857
AssertionError: expected +0 to be 1 // Object.is equality - Expected + Received - 1 + 0 ❯ src/tests/e2e.test.ts:857:34
src/tests/e2e.test.ts > livekit-rtc e2e > resume preserves the agent publication and does not fire Reconnected: packages/livekit-rtc/src/tests/e2e.test.ts#L777
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/tests/e2e.test.ts:777:34
Test (latest)
The strategy configuration was canceled because "test._24" failed
Test (latest)
The operation was canceled.
src/tests/e2e.test.ts > livekit-rtc e2e > full reconnect fires Reconnected once and ends with one publication: packages/livekit-rtc/src/tests/e2e.test.ts#L857
AssertionError: expected +0 to be 1 // Object.is equality - Expected + Received - 1 + 0 ❯ src/tests/e2e.test.ts:857:34
src/tests/e2e.test.ts > livekit-rtc e2e > resume preserves the agent publication and does not fire Reconnected: packages/livekit-rtc/src/tests/e2e.test.ts#L777
AssertionError: expected 1 to be +0 // Object.is equality - Expected + Received - 0 + 1 ❯ src/tests/e2e.test.ts:777:34
Formatting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
Test (24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
Test (22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
Test (20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/
Test (latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. 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/