1) tests/contextmenu.spec.ts:116:7 › context menu › pressing F2 should start rename for layer ──── Test timeout of 10000ms exceeded.

1) tests/contextmenu.spec.ts:116:7 › context menu › pressing F2 should start rename for layer ──── Error: locator.click: Page closed =========================== logs =========================== waiting for getByLabel('Layers', { exact: true }).getByText('Open Topo Map') ============================================================ 118 | .getByLabel('Layers', { exact: true }) 119 | .getByText('Open Topo Map') > 120 | .click(); | ^ 121 | await page 122 | .getByLabel('Layers', { exact: true }) 123 | .getByText('Open Topo Map') at /home/runner/work/jupytergis/jupytergis/ui-tests/tests/contextmenu.spec.ts:120:8

2) tests/contextmenu.spec.ts:205:7 › context menu › move layer to new group ────────────────────── Test timeout of 10000ms exceeded.

2) tests/contextmenu.spec.ts:205:7 › context menu › move layer to new group ────────────────────── Error: locator.click: Target closed =========================== logs =========================== waiting for getByLabel('Layers', { exact: true }).getByText('Open Topo Map') ============================================================ 207 | .getByLabel('Layers', { exact: true }) 208 | .getByText('Open Topo Map') > 209 | .click({ button: 'right' }); | ^ 210 | 211 | await page.getByText('Move Layers to Group').hover(); 212 | await page.getByText('Move Layers to New Group').click(); at /home/runner/work/jupytergis/jupytergis/ui-tests/tests/contextmenu.spec.ts:209:8

3) tests/left-panel.spec.ts:105:9 › #layerPanel › with GIS document › should navigate in nested groups Error: Timed out 5000ms waiting for expect(locator).toHaveCount(expected) Locator: locator('#jupytergis\\:\\:leftControlPanel').locator('.jp-gis-layerPanel').locator('.jp-gis-layerItem') Expected: 2 Received: 1 Call log: - expect.toHaveCount with timeout 5000ms - waiting for locator('#jupytergis\\:\\:leftControlPanel').locator('.jp-gis-layerPanel').locator('.jp-gis-layerItem') - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" - locator resolved to 1 element - unexpected value "1" 107 | const layerEntries = layerTree.locator('.jp-gis-layerItem'); 108 | > 109 | await expect(layerEntries).toHaveCount(2); | ^ 110 | await expect(layerEntries.first()).toHaveClass(/jp-gis-layer/); 111 | await expect(layerEntries.last()).toHaveClass(/jp-gis-layerGroup/); 112 | at /home/runner/work/jupytergis/jupytergis/ui-tests/tests/left-panel.spec.ts:109:34

4) tests/left-panel.spec.ts:152:9 › #layerPanel › with GIS document › should have visibility icon Error: Timed out 5000ms waiting for expect(locator).toHaveCount(expected) Locator: locator('#jupytergis\\:\\:leftControlPanel').locator('.jp-gis-layerPanel').getByTitle('Hide layer') Expected: 1 Received: 0 Call log: - expect.toHaveCount with timeout 5000ms - waiting for locator('#jupytergis\\:\\:leftControlPanel').locator('.jp-gis-layerPanel').getByTitle('Hide layer') - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" - locator resolved to 0 elements - unexpected value "0" 155 | const showLayerButton = layerTree.getByTitle('Show layer'); 156 | > 157 | await expect(hideLayerButton).toHaveCount(1); | ^ 158 | await expect(showLayerButton).toHaveCount(0); 159 | 160 | expect(await hideLayerButton.screenshot()).toMatchSnapshot( at /home/runner/work/jupytergis/jupytergis/ui-tests/tests/left-panel.spec.ts:157:37

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/cache@v2, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4, actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/cache@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/deploy-pages@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "extension-artifacts", "github-pages", "jupytergis-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/