1) [chromium] › tests/e2e/features/alerts.spec.ts:631:7 › Alert Creation › should create a between-threshold alert from a dashboard tile and verify on the alerts page @alerts @full-stack @full-stack › Save the tile with the alert configured TimeoutError: locator.waitFor: Timeout 10000ms exceeded. Call log: - waiting for getByTestId('chart-save-button') to be hidden 25 × locator resolved to visible <button type="button" data-variant="primary" data-testid="chart-save-button" class="mantine-focus-auto mantine-active m_77c9d27d mantine-Button-root m_87cf2631 mantine-UnstyledButton-root">…</button> at components/ChartEditorComponent.ts:932 930 | await this.saveButton.click(); 931 | // The modal closes once the dashboard mutation resolves. > 932 | await this.saveButton.waitFor({ state: 'hidden', timeout: 10000 }); | ^ 933 | } 934 | 935 | /** at ChartEditorComponent.save (/home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/components/ChartEditorComponent.ts:932:27) at /home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/features/alerts.spec.ts:683:9 at /home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/features/alerts.spec.ts:682:7

1) [chromium] › tests/e2e/features/dashboard.spec.ts:312:7 › Dashboard › should warn when closing tile editor with unsaved changes @dashboard Error: expect(locator).toBeAttached() failed Locator: getByRole('dialog').filter({ has: getByTestId('confirm-confirm-button') }) Expected: attached Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeAttached" with timeout 5000ms - waiting for getByRole('dialog').filter({ has: getByTestId('confirm-confirm-button') }) 315 | 316 | await dashboardPage.page.keyboard.press('Escape'); > 317 | await expect(dashboardPage.unsavedChangesConfirmModal).toBeAttached({ | ^ 318 | timeout: 5000, 319 | }); 320 | at /home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/features/dashboard.spec.ts:317:60

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache/restore@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

1 flaky [chromium] › tests/e2e/features/alerts.spec.ts:631:7 › Alert Creation › should create a between-threshold alert from a dashboard tile and verify on the alerts page @alerts @full-stack @full-stack 116 passed (9.3m)

1 skipped 115 passed (9.7m)

117 passed (9.8m)