1) [chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('button', { name: 'Options for Submenu' }) ============================================================ 268 | 269 | // Open the options menu. > 270 | await submenuOptions.click(); | ^ 271 | 272 | // usage of `page` is required because the options menu is rendered into a slot 273 | // outside of the treegrid. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:270:24

2) [chromium] › editor/blocks/navigation-list-view.spec.js:297:2 › Navigation block - List view editing › can edit menu items TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('link', { name: 'Page', includeHidden: true }).getByText('Top Level Item 1') ============================================================ 314 | } ) 315 | .getByText( 'Top Level Item 1' ); > 316 | await firstMenuItemAnchor.click(); | ^ 317 | 318 | // Get the settings panel. 319 | const blockSettings = page.getByRole( 'region', { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:316:29

3) [chromium] › editor/blocks/navigation.spec.js:127:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my most recently created 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="Menu 2 Link"') 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="Menu 2 Link"') 164 | `role=textbox[name="Navigation link text"i] >> text="Menu 2 Link"` 165 | ) > 166 | ).toBeVisible(); | ^ 167 | 168 | // Check the block in the frontend. 169 | await page.goto( `/?p=${ postId }` ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:166:6

3) [chromium] › editor/blocks/navigation.spec.js:127:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my most recently created menu Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="Menu 2 Link"') 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="Menu 2 Link"') 164 | `role=textbox[name="Navigation link text"i] >> text="Menu 2 Link"` 165 | ) > 166 | ).toBeVisible(); | ^ 167 | 168 | // Check the block in the frontend. 169 | await page.goto( `/?p=${ postId }` ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:166:6

11 skipped 152 passed (7.0m)

4 skipped 157 passed (7.4m)

3 skipped 129 passed (7.3m)

189 passed (7.5m)

162 passed (7.5m)

1 skipped 162 passed (7.1m)

165 passed (7.8m)

3 flaky [chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items [chromium] › editor/blocks/navigation-list-view.spec.js:297:2 › Navigation block - List view editing › can edit menu items [chromium] › editor/blocks/navigation.spec.js:127:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to my most recently created menu 1 skipped 158 passed (8.4m)

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/.