2) [chromium] › test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:119:2 › Dataviews List Layout › Actions are reachable via RIGHT/LEFT arrow keys Error: expect(locator).toBeFocused() failed Locator: getByRole('row', { name: 'Privacy Policy Edit Actions' }).getByRole('button', { name: 'Edit' }) Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for getByRole('row', { name: 'Privacy Policy Edit Actions' }).getByRole('button', { name: 'Edit' }) 9 × locator resolved to <button type="button" tabindex="-1" class="components-button is-small" id="view-list-0-495-primary-action-edit-post">Edit</button> - unexpected value "inactive" 138 | .getByRole( 'row', { name: 'Privacy Policy Edit Actions' } ) 139 | .getByRole( 'button', { name: 'Edit' } ) > 140 | ).toBeFocused(); | ^ 141 | 142 | await page.keyboard.press( 'ArrowRight' ); 143 | await expect( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:140:5

1) [chromium] › test/e2e/specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted › Paragraph and Group blocks are available in the inserter TimeoutError: locator.getAttribute: Timeout 10000ms exceeded. Call log: - waiting for locator('[name="editor-canvas"]').contentFrame().getByText('Initial content') at ../../../packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26 24 | : endSelectorOrLocator; 25 | > 26 | const startClientId = await startBlock.getAttribute( 'data-block' ); | ^ 27 | const endClientId = await endBlock?.getAttribute( 'data-block' ); 28 | 29 | if ( endClientId ) { at Editor.selectBlocks (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26:41) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:163:18 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:159:15

1) [chromium] › test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks › Save post and verify migration was written to database Error: expect(received).toContain(expected) // indexOf Expected substring: "\"submenuVisibility\":\"click\"" Received string: "<!-- wp:navigation {\"openSubmenusOnClick\":true,\"overlayMenu\":\"never\"} --> <!-- wp:navigation-submenu {\"label\":\"Products\"} --> <!-- wp:navigation-link {\"label\":\"Product 1\",\"url\":\"#\"} /--> <!-- wp:navigation-link {\"label\":\"Product 2\",\"url\":\"#\"} /--> <!-- /wp:navigation-submenu --> <!-- wp:navigation-link {\"label\":\"About\",\"url\":\"#\"} /--> <!-- /wp:navigation -->" 613 | const content = savedPost.content.raw; 614 | > 615 | expect( content ).toContain( '"submenuVisibility":"click"' ); | ^ 616 | expect( content ).not.toContain( 'openSubmenusOnClick' ); 617 | } ); 618 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:615:23 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:593:4

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/upload-artifact/merge@330a01c490aca151604b8cf639adc76d48f6c5d4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: actions/download-artifact@018cc2cf5baa6db3ef3c5f8a56943fffe632ef53. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 skipped 235 passed (12.1m)

2 flaky [chromium] › test/e2e/specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted [chromium] › test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:119:2 › Dataviews List Layout › Actions are reachable via RIGHT/LEFT arrow keys 5 skipped 232 passed (12.1m)

3 skipped 239 passed (10.8m)

1 flaky [chromium] › test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks 1 skipped 247 passed (13.2m)

1 skipped 235 passed (12.3m)

5 skipped 199 passed (13.2m)

6 skipped 266 passed (16.4m)