Process completed with exit code 1.

1) [chromium] › tests/e2e/specs/library-view.spec.js:134:2 › Library View Toggle › applying filters preserves the current view Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByRole('button', { name: 'Apply Filters' }) - locator resolved to <input type="submit" value="Apply Filters" class="viz-filter button button-secondary"/> - 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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 19 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms 138 | 139 | // Submit the filter form — the hidden view input should carry list view through. > 140 | await page.getByRole( 'button', { name: 'Apply Filters' } ).click(); | ^ 141 | await waitForLibraryToLoad( page ); 142 | 143 | await expect( page.locator( '#visualizer-library.view-list' ) ).toBeVisible(); at /home/runner/work/visualizer/visualizer/tests/e2e/specs/library-view.spec.js:140:63

1) [chromium] › tests/e2e/specs/library-view.spec.js:134:2 › Library View Toggle › applying filters preserves the current view Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByRole('button', { name: 'Apply Filters' }) - locator resolved to <input type="submit" value="Apply Filters" class="viz-filter button button-secondary"/> - 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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 19 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms 138 | 139 | // Submit the filter form — the hidden view input should carry list view through. > 140 | await page.getByRole( 'button', { name: 'Apply Filters' } ).click(); | ^ 141 | await waitForLibraryToLoad( page ); 142 | 143 | await expect( page.locator( '#visualizer-library.view-list' ) ).toBeVisible(); at /home/runner/work/visualizer/visualizer/tests/e2e/specs/library-view.spec.js:140:63

1) [chromium] › tests/e2e/specs/library-view.spec.js:134:2 › Library View Toggle › applying filters preserves the current view TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByRole('button', { name: 'Apply Filters' }) - locator resolved to <input type="submit" value="Apply Filters" class="viz-filter button button-secondary"/> - 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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</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 - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 19 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <h3>The Editor has a new home</h3> from <div id="wp-pointer-0" class="wp-pointer wp-pointer-top">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms 138 | 139 | // Submit the filter form — the hidden view input should carry list view through. > 140 | await page.getByRole( 'button', { name: 'Apply Filters' } ).click(); | ^ 141 | await waitForLibraryToLoad( page ); 142 | 143 | await expect( page.locator( '#visualizer-library.view-list' ) ).toBeVisible(); at /home/runner/work/visualizer/visualizer/tests/e2e/specs/library-view.spec.js:140:63

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/