Process completed with exit code 1.

2) tests/chat-save-restore.spec.ts:105:7 › #chatSaveRestore › should restore messages after page reload Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: page.evaluate: Execution context was destroyed, most likely because of a navigation. at /home/runner/work/ai/ai/ui-tests/node_modules/@jupyterlab/galata/src/jupyterlabpage.ts:717:17 at Timeout.check (/home/runner/work/ai/ai/ui-tests/node_modules/@jupyterlab/galata/src/utils.ts:183:33)

2) tests/chat-save-restore.spec.ts:105:7 › #chatSaveRestore › should restore messages after page reload Error: expect(locator).toHaveCount(expected) failed Locator: locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') Expected: 1 Received: 0 Call log: - Expect "toHaveCount" with timeout 120000ms - waiting for locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') 30 × locator resolved to 0 elements - unexpected value "0" 122 | await expect( 123 | panel.locator('.jp-chat-message-header:has-text("Jupyternaut")') > 124 | ).toHaveCount(1, { timeout: EXPECT_TIMEOUT }); | ^ 125 | 126 | // Save the chat. 127 | await panel.locator('.jp-ai-SaveButton').getByTitle('Save chat').click(); at /home/runner/work/ai/ai/ui-tests/tests/chat-save-restore.spec.ts:124:7

2) tests/chat-save-restore.spec.ts:105:7 › #chatSaveRestore › should restore messages after page reload Test timeout of 30000ms exceeded.

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveCount(expected) failed Locator: locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') Expected: 1 Received: 0 Call log: - Expect "toHaveCount" with timeout 120000ms - waiting for locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') 30 × locator resolved to 0 elements - unexpected value "0" 237 | await expect( 238 | panel.locator('.jp-chat-message-header:has-text("Jupyternaut")') > 239 | ).toHaveCount(1, { timeout: EXPECT_TIMEOUT }); | ^ 240 | 241 | // Wait for the debounced auto-save (3 s debounce + buffer). 242 | await page.waitForTimeout(4000); at /home/runner/work/ai/ai/ui-tests/tests/chat-save-restore.spec.ts:239:7

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveCount(expected) failed Locator: locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message') Expected: 2 Received: 1 Call log: - Expect "toHaveCount" with timeout 10000ms - waiting for locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message') 12 × locator resolved to 1 element - unexpected value "1" 259 | 260 | // The messages should have been restored. > 261 | await expect(reloadedPanel.locator('.jp-chat-message')).toHaveCount(2, { | ^ 262 | timeout: 10000 263 | }); 264 | }); at /home/runner/work/ai/ai/ui-tests/tests/chat-save-restore.spec.ts:261:61

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Error: expect(locator).toHaveCount(expected) failed Locator: locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') Expected: 1 Received: 0 Call log: - Expect "toHaveCount" with timeout 120000ms - waiting for locator('[id="@jupyterlite/ai:chat-panel"]').locator('.jp-chat-message-header:has-text("Jupyternaut")') 29 × locator resolved to 0 elements - unexpected value "0" 237 | await expect( 238 | panel.locator('.jp-chat-message-header:has-text("Jupyternaut")') > 239 | ).toHaveCount(1, { timeout: EXPECT_TIMEOUT }); | ^ 240 | 241 | // Wait for the debounced auto-save (3 s debounce + buffer). 242 | await page.waitForTimeout(4000); at /home/runner/work/ai/ai/ui-tests/tests/chat-save-restore.spec.ts:239:7

1) tests/chat-save-restore.spec.ts:218:7 › #chatSaveRestore › should save and restore autosave state and messages Test timeout of 30000ms exceeded.

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