1) [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › aria-disabled is correctly hydrated for different values Error: expect(received).toEqual(expected) // deep equality - Expected - 1 + Received + 1 Array [ "false", - "false", + null, ] 216 | name 217 | ); > 218 | expect( [ type, hydratedAttr ] ).toEqual( [ | ^ 219 | type, 220 | attrValue, 221 | ] ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:218:39

1) [webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:91:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit) TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('region', { name: 'Editor top bar' }).getByRole('button', { name: 'Save', exact: true }) locator resolved to <button type="button" aria-label="Save" aria-disabled="f…>Save</button> attempting click action waiting for element to be visible, enabled and stable element was detached from the DOM, retrying ============================================================ at ../../../packages/e2e-test-utils-playwright/src/editor/site-editor.ts:20 18 | await editorTopBar 19 | .getByRole( 'button', { name: 'Save', exact: true } ) > 20 | .click(); | ^ 21 | 22 | // Second Save button in the entities panel. 23 | await savePanel at Editor.saveSiteEditorEntities (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/site-editor.ts:20:4) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:42:17

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

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

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

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

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

1) [chromium] › editor/various/mentions.spec.js:42:2 › autocomplete mentions › should insert mention between two other words Test finished within timeout of 100000ms, but tearing down "context" ran out of time. Please allow more time for the test, since teardown is attributed towards the test timeout budget.

1) [chromium] › editor/various/mentions.spec.js:42:2 › autocomplete mentions › should insert mention between two other words Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── { code: 'existing_user_login', message: 'Sorry, that username already exists!', data: null }

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

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

3 skipped 129 passed (7.7m)

1 skipped 162 passed (7.9m)

1 flaky [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › aria-disabled is correctly hydrated for different values 4 skipped 156 passed (7.9m)

1 flaky [webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:91:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit) 188 passed (8.1m)

11 skipped 152 passed (7.9m)

165 passed (8.3m)

3 flaky [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 [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 158 passed (8.8m)