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

3) [chromium] › specs/site-editor/dataviews-list-layout-keyboard.spec.js:62:2 › Dataviews List Layout › Navigates from items list to preview via TAB, and vice versa Error: expect(locator).toBeFocused() failed Locator: getByRole('grid').getByRole('button').first() Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for getByRole('grid').getByRole('button').first() 9 × locator resolved to <button type="button" aria-pressed="false" data-active-item="true" id="view-list-0-525-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-525-label" aria-describedby="view-list-0-525-description"></button> - unexpected value "inactive" 79 | await expect( page.getByRole( 'grid' ) ).toBeVisible(); 80 | await page.keyboard.press( 'Tab' ); > 81 | await expect( firstItem ).toBeFocused(); | ^ 82 | 83 | // Go to the preview. 84 | await page.keyboard.press( 'Tab' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:81:29

2) [chromium] › specs/editor/various/publish-panel.spec.js:11:2 › Post publish panel › should move focus back to the Publish panel toggle button when canceling Error: expect(locator).toBeFocused() failed Locator: locator('role=region[name="Editor top bar"i]').locator('role=button[name="Publish"i]') Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for locator('role=region[name="Editor top bar"i]').locator('role=button[name="Publish"i]') 9 × locator resolved to <button type="button" aria-expanded="true" aria-disabled="false" class="components-button editor-post-publish-panel__toggle editor-post-publish-button__button is-primary is-compact">Publish</button> - unexpected value "inactive" 31 | 32 | // Test focus is moved back to the Publish panel toggle button. > 33 | await expect( publishPanelToggleButton ).toBeFocused(); | ^ 34 | } ); 35 | 36 | test( 'should move focus back to the Publish panel toggle button after publishing and closing the panel', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/publish-panel.spec.js:33:44

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/editor/various/multi-entity-saving.spec.js:28:2 › Editor - Multi-entity save flow › Save flow should work as expected Error: expect(locator).toBeDisabled() failed Locator: getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Saved' }) Expected: disabled Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeDisabled" with timeout 5000ms - waiting for getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Saved' }) 125 | await expect( 126 | topBar.getByRole( 'button', { name: 'Saved' } ) > 127 | ).toBeDisabled(); | ^ 128 | await expect( openSavePanel ).toBeHidden(); 129 | 130 | await editor.publishPost(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/multi-entity-saving.spec.js:127:5

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 (8.9m)

3 skipped 242 passed (12.0m)

6 skipped 243 passed (13.0m)

3 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 [chromium] › specs/editor/various/publish-panel.spec.js:11:2 › Post publish panel › should move focus back to the Publish panel toggle button when canceling [chromium] › specs/site-editor/dataviews-list-layout-keyboard.spec.js:62:2 › Dataviews List Layout › Navigates from items list to preview via TAB, and vice versa 5 skipped 233 passed (13.5m)

250 passed (13.3m)

1 flaky [chromium] › specs/editor/various/multi-entity-saving.spec.js:28:2 › Editor - Multi-entity save flow › Save flow should work as expected 1 skipped 246 passed (13.5m)

5 skipped 241 passed (17.1m)