Process completed with exit code 1.

3) [chromium] › tests/posts/kind.spec.ts:23:3 › Post kind filter › page posts should not appear in public news list, admin should show type and filter TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByTestId('markdown-editor') 37 | 38 | await page.getByRole('button', { name: 'Suivant' }).click() > 39 | await page.getByTestId('markdown-editor').click() | ^ 40 | await page.getByTestId('markdown-editor').fill('Contenu de l\'actualité') 41 | await page.getByTestId('markdown-editor').press('Tab') 42 | await page.waitForTimeout(500) at /__w/cdata/cdata/tests/posts/kind.spec.ts:39:47

2) [chromium] › tests/datasets/[did].spec.ts:103:1 › discussions tab navigates to discussions page TimeoutError: page.waitForLoadState: Timeout 30000ms exceeded. 106 | ) 107 | // Wait for Vue hydration before clicking NuxtLink (fix flaky test on Firefox) > 108 | await page.waitForLoadState('networkidle') | ^ 109 | 110 | const discussionsTab = page.getByRole('link', { name: /Discussions/ }) 111 | await discussionsTab.click() at /__w/cdata/cdata/tests/datasets/[did].spec.ts:108:14

1) [chromium] › tests/dataservices/creation.spec.ts:4:1 › can create a dataservice ─────────────── Error: Console errors/warnings: TypeError: Cannot read properties of null (reading 'id') at http://localhost:3000/_nuxt/DDsCPRjS.js:1:3863 at http://localhost:3000/_nuxt/DDsCPRjS.js:1:3863 at Object.base.extend.assertNoConsoleErrors.auto (/__w/cdata/cdata/tests/base.ts:57:13)

Process completed with exit code 1.

3) [firefox] › tests/datasets/[did].spec.ts:138:1 › quality tooltip displays content and link is clickable TimeoutError: page.waitForLoadState: Timeout 30000ms exceeded. 141 | ) 142 | // Wait for Vue hydration before clicking the toggletip (try fix flaky test on Firefox) > 143 | await page.waitForLoadState('networkidle') | ^ 144 | 145 | const qualityButton = page.getByRole('button', { name: 'Qualité des métadonnées' }).first() 146 | await expect(qualityButton).toBeVisible() at /__w/cdata/cdata/tests/datasets/[did].spec.ts:143:14

2) [firefox] › tests/datasets/[did].spec.ts:31:1 › dataset labels have proper tooltips and information TimeoutError: page.waitForLoadState: Timeout 30000ms exceeded. 36 | ) 37 | // Wait for Vue hydration before clicking the toggletip (try fix flaky test on Firefox) > 38 | await page.waitForLoadState('networkidle') | ^ 39 | 40 | await page.getByTestId('label-toggletip-button').click() 41 | await expect(page.getByTestId('label-toggletip-content')).toBeVisible() at /__w/cdata/cdata/tests/datasets/[did].spec.ts:38:14

1) [firefox] › tests/dataservices/[did].spec.ts:28:1 › discussions tab is accessible ───────────── TimeoutError: page.waitForLoadState: Timeout 30000ms exceeded. 29 | await page.goto(`/dataservices/${DATASERVICE_SLUG}`) 30 | // Wait for Vue hydration before clicking NuxtLink (fix flaky test on Firefox) > 31 | await page.waitForLoadState('networkidle') | ^ 32 | 33 | const discussionsTab = page.getByRole('link', { name: /Discussions/ }) 34 | await expect(discussionsTab).toBeVisible() at /__w/cdata/cdata/tests/dataservices/[did].spec.ts:31:14

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

Variable 'extensions' is already declared in the upper scope

Variable 'dataset' is already declared in the upper scope

Variable 'pageData' is already declared in the upper scope

Variable 'resourcesPage' is already declared in the upper scope

Variable 'dataservice' is already declared in the upper scope

Variable 'pageData' is already declared in the upper scope

Variable 'pageData' is already declared in the upper scope

'v-html' directive can lead to XSS attack

'v-html' directive can lead to XSS attack

'v-html' directive can lead to XSS attack

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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: astral-sh/setup-uv@v6, 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: astral-sh/setup-uv@v6, 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/

3 failed [chromium] › tests/dataservices/creation.spec.ts:4:1 › can create a dataservice ──────────────── [chromium] › tests/datasets/[did].spec.ts:103:1 › discussions tab navigates to discussions page [chromium] › tests/posts/kind.spec.ts:23:3 › Post kind filter › page posts should not appear in public news list, admin should show type and filter 98 passed (5.6m)