1) tests/chat-file.spec.ts:166:7 › #ychat › should add an id to the chat metadata ──────────────── Test timeout of 60000ms exceeded.

1) tests/chat-file.spec.ts:166:7 › #ychat › should add an id to the chat metadata ──────────────── Error: proxy.evaluate: Target page, context or browser has been closed 30 | filename: string 31 | ): Promise<Contents.IModel> => { > 32 | return await page.evaluate(async filepath => { | ^ 33 | return await window.jupyterapp.serviceManager.contents.get(filepath); 34 | }, filename); 35 | }; at readFileContent (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/tests/chat-file.spec.ts:32:21) at hasId (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/tests/chat-file.spec.ts:173:27) at Timeout.check (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/node_modules/@jupyterlab/galata/src/utils.ts:183:33)

2) tests/message-toolbar.spec.ts:96:7 › #messageToolbar › should cancel message edition ────────── Test timeout of 60000ms exceeded.

2) tests/message-toolbar.spec.ts:96:7 › #messageToolbar › should cancel message edition ────────── Error: locator.hover: Test timeout of 60000ms exceeded. Call log: - waiting for getByRole('main').getByRole('tabpanel', { name: 'my-chat.chat' }).locator('.jp-chat-messages-container .jp-chat-message').first().locator('.jp-chat-rendered-markdown') 102 | 103 | // Should display the message toolbar > 104 | await messageContent.hover({ position: { x: 5, y: 5 } }); | ^ 105 | await messageContent.locator('.jp-chat-toolbar jp-button').first().click(); 106 | 107 | await expect(messageContent).not.toBeVisible(); at /home/runner/work/jupyter-chat/jupyter-chat/ui-tests/tests/message-toolbar.spec.ts:104:26

3) tests/ui-config.spec.ts:198:7 › #typingNotification › should display typing user ────────────── Error: Timed out 5000ms waiting for expect(locator).toBeAttached() Locator: getByRole('main').getByRole('tabpanel', { name: 'my-chat.chat' }).locator('.jp-chat-writers') Expected: attached Received: <element(s) not found> Call log: - expect.toBeAttached with timeout 5000ms - waiting for getByRole('main').getByRole('tabpanel', { name: 'my-chat.chat' }).locator('.jp-chat-writers') 206 | 207 | await guestInput.press('a'); > 208 | await expect(writers).toBeAttached(); | ^ 209 | const start = Date.now(); 210 | await expect(writers).toHaveText(/jovyan_2 is writing/); 211 | await expect(writers).not.toBeAttached(); at /home/runner/work/jupyter-chat/jupyter-chat/ui-tests/tests/ui-config.spec.ts:208:27

3) tests/ui-config.spec.ts:198:7 › #typingNotification › should display typing user ────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.

3) tests/ui-config.spec.ts:198:7 › #typingNotification › should display typing user ────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.isChecked: Target page, context or browser has been closed at tests/test-utils.ts:51 49 | const tabName = splitPath[splitPath.length - 1]; 50 | await page.waitForCondition( > 51 | async () => await page.activity.isTabActive(tabName) | ^ 52 | ); 53 | panel = await page.activity.getPanelLocator(tabName); 54 | at Object.isInSimpleMode (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/node_modules/@jupyterlab/galata/src/utils.ts:311:17) at ActivityHelper.isTabActive (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/node_modules/@jupyterlab/galata/src/helpers/activity.ts:46:21) at /home/runner/work/jupyter-chat/jupyter-chat/ui-tests/tests/test-utils.ts:51:37 at Timeout.check (/home/runner/work/jupyter-chat/jupyter-chat/ui-tests/node_modules/@jupyterlab/galata/src/utils.ts:183:33)

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "jupyterlab_chat-artifacts", "jupyterlab_chat-notebook-playwright-tests", "jupyterlab_chat-playwright-tests". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/