1) [app-router] › tests/e2e/app-router/error-interactive.spec.ts:51:7 › Error boundary interactive behavior › can trigger error again after reset Error: page.click: Test timeout of 30000ms exceeded. Call log: - waiting for locator('#error-boundary button') - locator resolved to <button>Try again</button> - attempting click action 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div data-testid="vinext-dev-error-backdrop">…</div> from <div id="__vinext_dev_error_overlay_root">…</div> subtree intercepts pointer events - retrying click action - waiting 20ms 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div data-testid="vinext-dev-error-backdrop">…</div> from <div id="__vinext_dev_error_overlay_root">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 37 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div data-testid="vinext-dev-error-backdrop">…</div> from <div id="__vinext_dev_error_overlay_root">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms - waiting for element to be visible, enabled and stable 57 | 58 | // Reset > 59 | await page.click("#error-boundary button"); | ^ 60 | await expect(page.locator('[data-testid="trigger-error"]')).toBeVisible({ 61 | timeout: 10_000, 62 | }); at /home/runner/work/vinext/vinext/tests/e2e/app-router/error-interactive.spec.ts:59:16

1) [app-router] › tests/e2e/app-router/error-interactive.spec.ts:51:7 › Error boundary interactive behavior › can trigger error again after reset Test timeout of 30000ms exceeded.

2 passed (6.4s)

38 passed (12.9s)

16 passed (9.3s)

1 passed (14.4s)

17 passed (12.1s)

13 passed (8.3s)

7 passed (11.4s)

22 passed (13.4s)

39 passed (21.1s)

100 passed (29.9s)

1 passed (12.1s)

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026