Fix freebuff e2e tests #7
jahoomafreebuff-e2e.yml
on: push
build-freebuff
1m 2s
Matrix: e2e
Annotations
18 errors and 9 warnings
|
e2e-slash-commands
Process completed with exit code 1.
|
|
error: expect(received).toContain(expected):
freebuff/e2e/tests/slash-commands.e2e.test.ts#L83
Expected to contain: "help"
Received: "\n"
at <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/slash-commands.e2e.***.ts:83:24)
|
|
e2e-code-edit
Process completed with exit code 1.
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
|
|
e2e-terminal-command
Process completed with exit code 1.
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
|
|
e2e-startup
Process completed with exit code 1.
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
at async <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/startup.e2e.***.ts:45:21)
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
|
|
e2e-help-command
Process completed with exit code 1.
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
at async <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/help-command.e2e.***.ts:67:21)
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
|
|
e2e-ads-behavior
Process completed with exit code 1.
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
at async <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/ads-behavior.e2e.***.ts:40:21)
|
|
error: Timed out after 30000ms waiting for CLI to be ready.:
freebuff/e2e/utils/freebuff-session.ts#L130
at waitForReady (/home/runner/work/***/***/freebuff/e2e/utils/freebuff-session.ts:130:15)
|
|
e2e-agent-startup
Process completed with exit code 1.
|
|
error: expect(received).not.toBe(expected):
freebuff/e2e/tests/agent-startup.e2e.test.ts#L117
Expected: not "error"
at <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/agent-startup.e2e.***.ts:117:38)
|
|
error: expect(received).not.toBe(expected):
freebuff/e2e/tests/agent-startup.e2e.test.ts#L73
Expected: not "error"
at <anonymous> (/home/runner/work/***/***/freebuff/e2e/***s/agent-startup.e2e.***.ts:73:38)
|
|
build-freebuff
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-slash-commands
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-code-edit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-terminal-command
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-startup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-help-command
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-ads-behavior
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
e2e-agent-startup
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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=*** 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=***. 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 | |
|---|---|---|---|
|
freebuff-binary
Expired
|
49.6 MB |
sha256:9c456c50bc6c48afaed23f0a15e6ff0d74b9169d33644cd749a64b2beb23836e
|
|
|
tmux-logs-ads-behavior
|
834 Bytes |
sha256:64a3745d05a4eea40c4404a0a4003d40f0da322b3a0cfae8450b4e6e7eaf4e0e
|
|
|
tmux-logs-agent-startup
|
837 Bytes |
sha256:8e66ce8770b7abe8d8dcdd1cc44cdac7ba45cd902c28d7f6874fe207c29451b7
|
|
|
tmux-logs-code-edit
|
432 Bytes |
sha256:a808f3da273f55b2f5bb85c1b97d5fb63f7439375e5dc028467e557ebcd20957
|
|
|
tmux-logs-help-command
|
839 Bytes |
sha256:928058f61bc74d1de8c99fdd0d5fcf40859ba262bd9ab804d0b3f3ccc8994f4d
|
|
|
tmux-logs-slash-commands
|
1.97 KB |
sha256:07122ce33bfd332765e3a617299a8c50d7893078a4724da2e4abe26e5e7a428a
|
|
|
tmux-logs-startup
|
838 Bytes |
sha256:1da95188102c8c8df62265358d5f5650a7c07bd9a5aeb5c05481122b6bc5a3db
|
|
|
tmux-logs-terminal-command
|
431 Bytes |
sha256:320dbcee160a909bb57c5ee4542740e2c15ad3247eb789322ebb02228b23f2a9
|
|