AssertionError: promise rejected "CloudApiError: Not found { …(2) }" instead of resolving ❯ src/live.e2e.test.ts:166:41 Caused by: Caused by: CloudApiError: Not found ❯ ElizaCloudHttpClient.request src/http.ts:266:11 ❯ src/live.e2e.test.ts:166:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { statusCode: 404, errorBody: { success: false, error: 'Not found', details: undefined, requiredCredits: undefined, quota: undefined } }

could not read Username for 'https://github.com': terminal prompts disabled

the remote end hung up unexpectedly

could not read Username for 'https://github.com': terminal prompts disabled

Process completed with exit code 1.

AssertionError: expected 'tool would also have something to say' to be 'All three counters reset to zero.' // Object.is equality Expected: "All three counters reset to zero." Received: "tool would also have something to say" ❯ src/runtime/__tests__/planner-loop-user-facing-text.test.ts:186:31

Process completed with exit code 1.

@elizaos/plugin-local-inference#test: command (/home/runner/work/eliza/eliza/plugins/plugin-local-inference) /home/runner/.bun/bin/bun run test exited (1)

Error: Failed to resolve entry for package "@elizaos/agent". The package may have incorrect main/module/exports specified in its package.json. ❯ src/routes/local-inference-compat-routes.test.ts:1:1

Process completed with exit code 1.

Required job 'plugin-tests' finished with 'failure' (expected success)

Required job 'server-tests' finished with 'failure' (expected success)

No remote capability provider endpoints configured - skipping optional provider live E2E.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/

Cloud Live E2E skipped because the configured external provider is unavailable.

No bun/install.js found; downstream bun run calls may fail

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/

No bun/install.js found; downstream bun run calls may fail

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/

No bun/install.js found; downstream bun run calls may fail

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/

No bun/install.js found; downstream bun run calls may fail

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. 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/

No bun/install.js found; downstream bun run calls may fail

Live-only job 'github-live-artifact-validate' was skipped for this PR context.