1) [chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page Error: locator.click: Error: strict mode violation: getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') }) resolved to 2 elements: 1) <div class="" id=":ru:" role="row">…</div> aka getByRole('row', { name: 'Sample Page Edit Actions Author Author avatar admin Status Published', exact: true }) 2) <div class="" id=":r16:" role="row">…</div> aka getByRole('row', { name: 'Sample page Edit Actions Author Author avatar admin Status Published', exact: true }) Call log: - waiting for getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') }) 91 | .filter( { has: samplePageTwo } ); 92 | // eslint-disable-next-line playwright/no-force-option > 93 | await samplePageTwoRow.click( { force: true } ); | ^ 94 | await samplePageTwoRow 95 | .getByRole( 'button', { 96 | name: 'Actions', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/homepage-settings.spec.js:93:26

1) [chromium] › 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] › specs/interactivity/router-regions.spec.ts:543:6 › Router regions › should be preserved on first navigation with `data-wp-key` and `attachTo` Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('region-1-ssr') Expected: "content from page attachTo2" Received: "content from page 1" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('region-1-ssr') 2 × locator resolved to <p data-testid="region-1-ssr">content from page attachTo1</p> - unexpected value "content from page attachTo1" 7 × locator resolved to <p data-testid="region-1-ssr">content from page 1</p> - unexpected value "content from page 1" 583 | // Navigate to "Page attachTo 2". 584 | await page.getByTestId( 'next' ).click(); > 585 | await expect( region1Ssr ).toHaveText( 'content from page attachTo2' ); | ^ 586 | 587 | // Regions with `data-wp-key` and other directives should not be recreated. 588 | for ( const regionId in regions ) { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-regions.spec.ts:585:30

1) [chromium] › 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

1 flaky [chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page 3 skipped 244 passed (11.5m)

3 skipped 242 passed (11.6m)

1 skipped 244 passed (13.0m)

1 flaky [chromium] › 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 5 skipped 233 passed (13.1m)

250 passed (13.1m)

1 flaky [chromium] › specs/interactivity/router-regions.spec.ts:543:6 › Router regions › should be preserved on first navigation with `data-wp-key` and `attachTo` 6 skipped 242 passed (14.5m)

1 flaky [chromium] › 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 260 passed (22.3m)