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

1) [chromium] › tests/e2e/features/search/relative-time.spec.ts:169:9 › Relative Time Picker › Live Mode Integration › should resume live tail with selected interval @relative-time › Pause live tail by selecting absolute time TimeoutError: locator.waitFor: Timeout 5000ms exceeded. Call log: - waiting for getByTestId('time-picker-relative-switch') at components/TimePickerComponent.ts:175 173 | */ 174 | async isRelativeTimeEnabled(): Promise<boolean> { > 175 | await this.relativeTimeSwitch.waitFor({ state: 'attached', timeout: 5000 }); | ^ 176 | return await this.relativeTimeSwitch.isChecked(); 177 | } 178 | at TimePickerComponent.isRelativeTimeEnabled (/home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/components/TimePickerComponent.ts:175:35) at TimePickerComponent.disableRelativeTime (/home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/components/TimePickerComponent.ts:193:34) at /home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/features/search/relative-time.spec.ts:178:37 at /home/runner/work/ClickStack/ClickStack/packages/app/tests/e2e/features/search/relative-time.spec.ts:176:7

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 skipped 115 passed (5.7m)

117 passed (5.8m)

1 flaky [chromium] › tests/e2e/features/dashboard.spec.ts:312:7 › Dashboard › should warn when closing tile editor with unsaved changes @dashboard 116 passed (6.2m)