1) [chromium] › editor/blocks/navigation-list-view.spec.js:385:2 › Navigation block - List view editing › can add submenus TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).locator('xpath=..').getByRole('button', { name: 'Options for Page Link' }) ============================================================ 417 | 418 | // Open the options menu. > 419 | await firstItemOptions.click(); | ^ 420 | 421 | // Add the submenu. 422 | // usage of `page` is required because the options menu is rendered into a slot at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:419:26

2) [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

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