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

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

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

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/validate-multiple-use.spec.js:12:2 › Validate multiple use › should display correct number of warning messages TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Options"]') ============================================================ at ../../../packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20 18 | const button = blockToolbar.locator( `role=button[name="${ label }"]` ); 19 | > 20 | await button.click(); | ^ 21 | } 22 | at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20:15) at Editor.clickBlockOptionsMenuItem (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-options-menu-item.ts:13:2) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/validate-multiple-use.spec.js:23:3

1) [chromium] › editor/various/validate-multiple-use.spec.js:12:2 › Validate multiple use › should display correct number of warning messages Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Options"]') ============================================================ at ../../../packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20 18 | const button = blockToolbar.locator( `role=button[name="${ label }"]` ); 19 | > 20 | await button.click(); | ^ 21 | } 22 | at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20:15) at Editor.clickBlockOptionsMenuItem (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-options-menu-item.ts:13:2) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/validate-multiple-use.spec.js:23:3

1) [chromium] › editor/various/validate-multiple-use.spec.js:12:2 › Validate multiple use › should display correct number of warning messages Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for locator('role=toolbar[name="Block tools"i]').locator('role=button[name="Options"]') ============================================================ at ../../../packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20 18 | const button = blockToolbar.locator( `role=button[name="${ label }"]` ); 19 | > 20 | await button.click(); | ^ 21 | } 22 | at Editor.clickBlockToolbarButton (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-toolbar-button.ts:20:15) at Editor.clickBlockOptionsMenuItem (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/click-block-options-menu-item.ts:13:2) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/validate-multiple-use.spec.js:23:3

Process completed with exit code 1.

1) [chromium] › editor/various/pattern-overrides.spec.js:497:2 › Pattern Overrides › resets overrides after clicking the reset button Error: The heading block should have the reset button enabled Timed out 5000ms waiting for expect(locator).toBeEnabled() Locator: getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) Expected: enabled Received: disabled Call log: - The heading block should have the reset button enabled with timeout 5000ms - waiting for getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) 553 | resetButton, 554 | 'The heading block should have the reset button enabled' > 555 | ).toBeEnabled(); | ^ 556 | 557 | // Assert the unmodified paragraph block (no overrides). 558 | await editor.selectBlocks( paragraphBlock ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/pattern-overrides.spec.js:555:5

1) [chromium] › editor/various/pattern-overrides.spec.js:497:2 › Pattern Overrides › resets overrides after clicking the reset button Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: The heading block should have the reset button enabled Timed out 5000ms waiting for expect(locator).toBeEnabled() Locator: getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) Expected: enabled Received: disabled Call log: - The heading block should have the reset button enabled with timeout 5000ms - waiting for getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) 553 | resetButton, 554 | 'The heading block should have the reset button enabled' > 555 | ).toBeEnabled(); | ^ 556 | 557 | // Assert the unmodified paragraph block (no overrides). 558 | await editor.selectBlocks( paragraphBlock ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/pattern-overrides.spec.js:555:5

1) [chromium] › editor/various/pattern-overrides.spec.js:497:2 › Pattern Overrides › resets overrides after clicking the reset button Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: The heading block should have the reset button enabled Timed out 5000ms waiting for expect(locator).toBeEnabled() Locator: getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) Expected: enabled Received: disabled Call log: - The heading block should have the reset button enabled with timeout 5000ms - waiting for getByRole('toolbar', { name: 'Block tools' }).getByRole('button', { name: 'Reset' }) 553 | resetButton, 554 | 'The heading block should have the reset button enabled' > 555 | ).toBeEnabled(); | ^ 556 | 557 | // Assert the unmodified paragraph block (no overrides). 558 | await editor.selectBlocks( paragraphBlock ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/pattern-overrides.spec.js:555:5

Process completed with exit code 1.

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

The operation was canceled.

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.6m)

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.0m)

11 skipped 152 passed (7.7m)

2 flaky [chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls [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 1 skipped 159 passed (8.4m)

1 failed [chromium] › editor/various/validate-multiple-use.spec.js:12:2 › Validate multiple use › should display correct number of warning messages 4 skipped 156 passed (8.6m)

1 failed [chromium] › editor/various/pattern-overrides.spec.js:497:2 › Pattern Overrides › resets overrides after clicking the reset button 1 skipped 161 passed (8.5m)