1) [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › name 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

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.spec.js:23:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to a list of pages if there are no menus Error: Timed out 10000ms waiting for expect(locator).toBeVisible() Locator: frameLocator('[name="editor-canvas"]').getByRole('document', { name: 'Block: Page List' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 10000ms - waiting for frameLocator('[name="editor-canvas"]').getByRole('document', { name: 'Block: Page List' }) 32 | } ); 33 | > 34 | await expect( pageListBlock ).toBeVisible( { | ^ 35 | // Wait for the Nav and Page List block API requests to resolve. 36 | // Note: avoid waiting on network requests as these are not perceivable 37 | // to the user. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:34:34

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

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

189 passed (7.7m)

165 passed (8.3m)

11 skipped 152 passed (8.2m)

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

1 skipped 162 passed (8.2m)

1 flaky [chromium] › editor/blocks/navigation.spec.js:23:3 › Navigation block › As a user I want the navigation block to fallback to the best possible default › default to a list of pages if there are no menus 1 skipped 160 passed (8.5m)