1) [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('tab', { name: 'List View' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('tab', { name: 'List View' }) 62 | name: 'List View', 63 | } ) > 64 | ).toBeVisible(); | ^ 65 | 66 | const listViewPanel = page.getByRole( 'tabpanel', { 67 | name: 'List View', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:64:5

1) [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('tab', { name: 'List View' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('tab', { name: 'List View' }) 62 | name: 'List View', 63 | } ) > 64 | ).toBeVisible(); | ^ 65 | 66 | const listViewPanel = page.getByRole( 'tabpanel', { 67 | name: 'List View', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:64:5

1) [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('tab', { name: 'List View' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('tab', { name: 'List View' }) 62 | name: 'List View', 63 | } ) > 64 | ).toBeVisible(); | ^ 65 | 66 | const listViewPanel = page.getByRole( 'tabpanel', { 67 | name: 'List View', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:64:5

2) [chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1') 110 | } ) 111 | .getByText( 'Top Level Item 1' ) > 112 | ).toBeVisible(); | ^ 113 | 114 | await expect( 115 | listView at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:112:5

3) [chromium] › editor/blocks/navigation.spec.js:49:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my only existing menu Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="WordPress"') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="WordPress"') 67 | `role=textbox[name="Navigation link text"i] >> text="WordPress"` 68 | ) > 69 | ).toBeVisible(); | ^ 70 | 71 | const postId = await editor.publishPost(); 72 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:69:6

4) [chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for frameLocator('[name="editor-canvas"]').getByRole('button', { name: 'Add block' }) ============================================================ 195 | name: 'Add block', 196 | } ); > 197 | await navBlockInserter.click(); | ^ 198 | 199 | await page.keyboard.type( 'https://example.com' ); 200 | await page.keyboard.press( 'Enter' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:197:27

5) [chromium] › editor/blocks/navigation.spec.js:217:3 › Navigation block › As a user I want to create submenus using the navigation block › submenu converts to link automatically Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="WordPress"') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="WordPress"') 234 | `role=textbox[name="Navigation link text"i] >> text="WordPress"` 235 | ) > 236 | ).toBeVisible(); | ^ 237 | 238 | const navigationBlock = editor.canvas.getByRole( 'document', { 239 | name: 'Block: Navigation', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:236:6

Process completed with exit code 1.

4 skipped 157 passed (7.9m)

11 skipped 152 passed (7.7m)

1 skipped 162 passed (8.0m)

189 passed (7.9m)

3 skipped 129 passed (8.1m)

165 passed (8.5m)

162 passed (8.9m)

1 failed [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls 4 flaky [chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure [chromium] › editor/blocks/navigation.spec.js:49:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my only existing menu [chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu [chromium] › editor/blocks/navigation.spec.js:217:3 › Navigation block › As a user I want to create submenus using the navigation block › submenu converts to link automatically 1 skipped 156 passed (9.2m)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.