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

2) [chromium] › editor/blocks/navigation.spec.js:91:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to the only existing classic menu if there are no block menus Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="Custom link"') Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for frameLocator('[name="editor-canvas"]').locator('role=textbox[name="Navigation link text"i]').locator('text="Custom link"') 112 | `role=textbox[name="Navigation link text"i] >> text="Custom link"` 113 | ) > 114 | ).toBeVisible( { timeout: 10000 } ); // allow time for network request. | ^ 115 | 116 | const postId = await editor.publishPost(); 117 | // Check the block in the frontend. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:114:6

1) [chromium] › interactivity/router-navigate.spec.ts:202:6 › Router navigate › should overwrite the state with the one serialized in the new page Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('prop1') Expected string: "link 1" Received string: "main" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('prop1') - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" 216 | // Old values not overwritten should remain the same. 217 | // New properties should appear. > 218 | await expect( prop1 ).toHaveText( 'link 1' ); | ^ 219 | await expect( prop2 ).toHaveText( 'main' ); 220 | await expect( prop3 ).toHaveText( 'link 1' ); 221 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:218:25

1) [chromium] › interactivity/router-navigate.spec.ts:202:6 › Router navigate › should overwrite the state with the one serialized in the new page Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('prop1') Expected string: "link 1" Received string: "main" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('prop1') - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" 216 | // Old values not overwritten should remain the same. 217 | // New properties should appear. > 218 | await expect( prop1 ).toHaveText( 'link 1' ); | ^ 219 | await expect( prop2 ).toHaveText( 'main' ); 220 | await expect( prop3 ).toHaveText( 'link 1' ); 221 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:218:25

1) [chromium] › interactivity/router-navigate.spec.ts:202:6 › Router navigate › should overwrite the state with the one serialized in the new page Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('prop1') Expected string: "link 1" Received string: "main" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('prop1') - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" 216 | // Old values not overwritten should remain the same. 217 | // New properties should appear. > 218 | await expect( prop1 ).toHaveText( 'link 1' ); | ^ 219 | await expect( prop2 ).toHaveText( 'main' ); 220 | await expect( prop3 ).toHaveText( 'link 1' ); 221 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:218:25

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

3 skipped 129 passed (7.3m)

4 skipped 158 passed (7.7m)

2 flaky [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:91:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to the only existing classic menu if there are no block menus 1 skipped 153 passed (7.7m)

157 passed (8.0m)

1 skipped 169 passed (7.8m)

171 passed (8.3m)

1 failed [chromium] › interactivity/router-navigate.spec.ts:202:6 › Router navigate › should overwrite the state with the one serialized in the new page 197 passed (7.8m)

11 skipped 169 passed (8.3m)

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