feat(cloud-shared): rebrand-ready agent base domain config (waifu.fun → elizacloud.ai prep) #3819
test.yml
on: pull_request
Cloud Live E2E (Eliza Cloud)
2m 21s
Remote Capability Provider Live E2E
3s
Server Tests
8m 25s
Client Tests
9m 48s
Plugin Tests
10m 39s
Electrobun Desktop Contract
5m 13s
All Tests Passed
2s
Annotations
9 errors, 13 warnings, and 1 notice
|
src/live.e2e.test.ts > ElizaCloudClient real API e2e: API-key read paths > lists containers, container quota, and Eliza agents:
packages/cloud-sdk/src/live.e2e.test.ts#L166
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 } }
|
|
Server Tests
Process completed with exit code 1.
|
|
src/runtime/__tests__/planner-loop-user-facing-text.test.ts > planner-loop — user-facing tool text isolation > does not regress evaluator's explicit messageToUser path:
packages/core/src/runtime/__tests__/planner-loop-user-facing-text.test.ts#L186
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
|
|
Plugin Tests
Canceling since a higher priority waiting request for test-refs/pull/7896/merge exists
|
|
Plugin Tests
The operation was canceled.
|
|
All Tests Passed
Process completed with exit code 1.
|
|
Test gate
Required job 'plugin-tests' finished with 'cancelled' (expected success)
|
|
Test gate
Required job 'server-tests' finished with 'failure' (expected success)
|
|
Tests
Canceling since a higher priority waiting request for test-refs/pull/7896/merge exists
|
|
Remote Capability Provider Live E2E
No remote capability provider endpoints configured - skipping optional provider live E2E.
|
|
Cloud Live E2E (Eliza Cloud)
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 (Eliza Cloud)
Cloud Live E2E skipped because the configured external provider is unavailable.
|
|
Cloud Live E2E (Eliza Cloud)
No bun/install.js found; downstream bun run calls may fail
|
|
Electrobun Desktop Contract
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/
|
|
Electrobun Desktop Contract
No bun/install.js found; downstream bun run calls may fail
|
|
Server Tests
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/
|
|
Server Tests
No bun/install.js found; downstream bun run calls may fail
|
|
Client Tests
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/
|
|
Client Tests
No bun/install.js found; downstream bun run calls may fail
|
|
Plugin Tests
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/
|
|
Plugin Tests
No bun/install.js found; downstream bun run calls may fail
|
|
Test gate
Live-only job 'github-live-artifact-validate' was skipped for this PR context.
|
|
Cloud Live E2E (Eliza Cloud)
Remote capability cloud sandbox live smoke is only observed on workflow_dispatch or schedule events.
|