Process completed with exit code 1.

2) [visual] › e2e/tests/visual/pages.spec.ts:27:3 › Visual - landing pages › settings rag configuration Error: A snapshot doesn't exist at /home/runner/work/rag/rag/frontend/e2e/tests/__snapshots__/visual/pages.spec.ts/settings-rag.png, writing actual. 29 | await settings.goto(); 30 | > 31 | await expect(page).toHaveScreenshot('settings-rag.png', { | ^ 32 | fullPage: true, 33 | maxDiffPixelRatio: 0.02, 34 | animations: 'disabled', at /home/runner/work/rag/rag/frontend/e2e/tests/visual/pages.spec.ts:31:5

1) [visual] › e2e/tests/visual/pages.spec.ts:15:3 › Visual - landing pages › chat empty state ──── Error: A snapshot doesn't exist at /home/runner/work/rag/rag/frontend/e2e/tests/__snapshots__/visual/pages.spec.ts/chat-empty-state.png, writing actual. 18 | await chat.goto(); 19 | > 20 | await expect(page).toHaveScreenshot('chat-empty-state.png', { | ^ 21 | fullPage: true, 22 | maxDiffPixelRatio: 0.02, 23 | animations: 'disabled', at /home/runner/work/rag/rag/frontend/e2e/tests/visual/pages.spec.ts:20:5

Process completed with exit code 1.

1) [chromium] › e2e/tests/navigation/navigation.spec.ts:17:3 › Navigation - top-level routes › settings toggle switches between / and /settings Error: expect(page).toHaveURL(expected) failed Expected pattern: /\/$/ Received string: "http://localhost:3000/settings" Timeout: 10000ms Call log: - Expect "toHaveURL" with timeout 10000ms 14 × unexpected value "http://localhost:3000/settings" 24 | 25 | await page.getByTestId('settings-toggle').click(); > 26 | await expect(page).toHaveURL(/\/$/); | ^ 27 | }); 28 | 29 | test('direct navigation to /collections/new renders the new-collection page', async ({ at /home/runner/work/rag/rag/frontend/e2e/tests/navigation/navigation.spec.ts:26:24

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, pnpm/action-setup@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/

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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/

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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/

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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/

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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/

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/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@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/

2 failed [visual] › e2e/tests/visual/pages.spec.ts:15:3 › Visual - landing pages › chat empty state ───── [visual] › e2e/tests/visual/pages.spec.ts:27:3 › Visual - landing pages › settings rag configuration

3 passed (10.3s)

30 passed (34.2s)

29 passed (47.6s)

1 failed [chromium] › e2e/tests/navigation/navigation.spec.ts:17:3 › Navigation - top-level routes › settings toggle switches between / and /settings 29 passed (39.5s)