1) [chromium] › site-editor/dataviews-list-layout-keyboard.spec.js:96:2 › Dataviews List Layout › Navigates the items list via UP/DOWN arrow keys Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByLabel('Sample Page') Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByLabel('Sample Page') - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" - locator resolved to <button tabindex="-1" type="button" aria-pressed="false" id="view-list-0-177-item-wrapper" class="dataviews-view-list__item" aria-labelledby="view-list-0-177-label" aria-describedby="view-list-0-177-description"></button> - unexpected value "not focused" 111 | // Use arrow up/down to move through the list. 112 | await page.keyboard.press( 'ArrowDown' ); > 113 | await expect( page.getByLabel( 'Sample Page' ) ).toBeFocused(); | ^ 114 | 115 | await page.keyboard.press( 'ArrowUp' ); 116 | await expect( page.getByLabel( 'Privacy Policy' ) ).toBeFocused(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/dataviews-list-layout-keyboard.spec.js:113:52

1) [chromium] › editor/blocks/navigation.spec.js:318:2 › Navigation block › navigation manages focus for creating, editing, and deleting items › should send focus to the newly created navigation link item when creating a link Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) Expected: focused Received: <element(s) not found> Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) 654 | 655 | const linkControlLink = await this.getLinkControlLink( label ); > 656 | await expect( linkControlLink ).toBeFocused(); | ^ 657 | 658 | await this.page.keyboard.press( 'Escape' ); 659 | at Navigation.addPage (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:656:35) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:350:4 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:348:3

1) [chromium] › editor/blocks/navigation.spec.js:318:2 › Navigation block › navigation manages focus for creating, editing, and deleting items › should send focus to the newly created navigation link item when creating a link Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) Expected: focused Received: <element(s) not found> Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) 654 | 655 | const linkControlLink = await this.getLinkControlLink( label ); > 656 | await expect( linkControlLink ).toBeFocused(); | ^ 657 | 658 | await this.page.keyboard.press( 'Escape' ); 659 | at Navigation.addPage (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:656:35) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:350:4 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:348:3

1) [chromium] › editor/blocks/navigation.spec.js:318:2 › Navigation block › navigation manages focus for creating, editing, and deleting items › should send focus to the newly created navigation link item when creating a link Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) Expected: focused Received: <element(s) not found> Call log: - expect.toBeFocused with timeout 5000ms - waiting for getByRole('link', { name: 'Cat (opens in a new tab)', exact: true }) 654 | 655 | const linkControlLink = await this.getLinkControlLink( label ); > 656 | await expect( linkControlLink ).toBeFocused(); | ^ 657 | 658 | await this.page.keyboard.press( 'Escape' ); 659 | at Navigation.addPage (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:656:35) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:350:4 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:348:3

2) [chromium] › editor/blocks/search.spec.js:23:2 › Search › should auto-configure itself to sensible defaults when inserted into a Navigation block Error: locator.click: Error: strict mode violation: getByRole('button', { name: 'Add block' }) resolved to 2 elements: 1) <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" aria-describedby="list-view-appender__0" class="components-button block-editor-inserter__toggle has-icon">…</button> aka getByLabel('Add block') 2) <button type="button" aria-haspopup="listbox" class="components-button is-next-40px-default-size has-text has-icon">…</button> aka getByText('Add block') Call log: - waiting for getByRole('button', { name: 'Add block' }) 45 | await navBlockInserter.click(); 46 | > 47 | await page.getByRole( 'button', { name: 'Add block' } ).click(); | ^ 48 | 49 | // Click on the Search block option. 50 | await page.getByRole( 'option', { name: 'Search' } ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/search.spec.js:47:59

2) [chromium] › editor/blocks/search.spec.js:23:2 › Search › should auto-configure itself to sensible defaults when inserted into a Navigation block Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Error: strict mode violation: getByRole('button', { name: 'Add block' }) resolved to 2 elements: 1) <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" aria-describedby="list-view-appender__0" class="components-button block-editor-inserter__toggle has-icon">…</button> aka getByLabel('Add block') 2) <button type="button" aria-haspopup="listbox" class="components-button is-next-40px-default-size has-text has-icon">…</button> aka getByText('Add block') Call log: - waiting for getByRole('button', { name: 'Add block' }) 45 | await navBlockInserter.click(); 46 | > 47 | await page.getByRole( 'button', { name: 'Add block' } ).click(); | ^ 48 | 49 | // Click on the Search block option. 50 | await page.getByRole( 'option', { name: 'Search' } ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/search.spec.js:47:59

2) [chromium] › editor/blocks/search.spec.js:23:2 › Search › should auto-configure itself to sensible defaults when inserted into a Navigation block Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Error: strict mode violation: getByRole('button', { name: 'Add block' }) resolved to 2 elements: 1) <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" aria-describedby="list-view-appender__0" class="components-button block-editor-inserter__toggle has-icon">…</button> aka getByLabel('Add block') 2) <button type="button" aria-haspopup="listbox" class="components-button is-next-40px-default-size has-text has-icon">…</button> aka getByText('Add block') Call log: - waiting for getByRole('button', { name: 'Add block' }) 45 | await navBlockInserter.click(); 46 | > 47 | await page.getByRole( 'button', { name: 'Add block' } ).click(); | ^ 48 | 49 | // Click on the Search block option. 50 | await page.getByRole( 'option', { name: 'Search' } ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/search.spec.js:47:59

Process completed with exit code 1.

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions TimeoutError: locator.waitFor: Timeout 60000ms exceeded. Call log: - waiting for locator('.edit-site-canvas-loader, .edit-site-canvas-spinner') to be visible at ../../../packages/e2e-test-utils-playwright/src/admin/visit-site-editor.ts:57 55 | // Wait for the canvas loader to appear first, so that the locator that 56 | // waits for the hidden state doesn't resolve prematurely. > 57 | await canvasLoader.waitFor( { state: 'visible', timeout: 60_000 } ); | ^ 58 | await canvasLoader.waitFor( { 59 | state: 'hidden', 60 | // Bigger timeout is needed for larger entities, like the Large Post at Admin.visitSiteEditor (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/admin/visit-site-editor.ts:57:22) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:353:4

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

2 skipped 200 passed (6.6m)

1 flaky [chromium] › site-editor/dataviews-list-layout-keyboard.spec.js:96:2 › Dataviews List Layout › Navigates the items list via UP/DOWN arrow keys 1 skipped 194 passed (9.6m)

2 failed [chromium] › editor/blocks/navigation.spec.js:318:2 › Navigation block › navigation manages focus for creating, editing, and deleting items [chromium] › editor/blocks/search.spec.js:23:2 › Search › should auto-configure itself to sensible defaults when inserted into a Navigation block 1 skipped 196 passed (9.7m)

1 skipped 201 passed (10.1m)

1 skipped 201 passed (10.2m)

199 passed (10.4m)

1 skipped 198 passed (9.9m)