DataViews: Fix patterns, templates and template parts pagination `z-i… #96916
end2end-test.yml
on: push
Matrix: e2e-playwright
Puppeteer
6m 49s
Report to GitHub
3m 48s
Annotations
11 errors, 10 warnings, and 8 notices
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › aria-disabled is correctly hydrated for different values:
test/e2e/specs/interactivity/directive-bind.spec.ts#L218
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
|
Playwright - 2
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
[chromium] › editor/blocks/navigation-list-view.spec.js:49:2 › Navigation block - List view editing › show a list view in the inspector controls:
test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L64
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
|
[chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure:
test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L112
2) [chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1')
110 | } )
111 | .getByText( 'Top Level Item 1' )
> 112 | ).toBeVisible();
| ^
113 |
114 | await expect(
115 | listView
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:112:5
|
[chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure:
test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L112
2) [chromium] › editor/blocks/navigation-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('gridcell', { name: 'Page Link' }).filter({ hasText: 'Block 1 of 2, Level 1' }).getByText('Top Level Item 1')
110 | } )
111 | .getByText( 'Top Level Item 1' )
> 112 | ).toBeVisible();
| ^
113 |
114 | await expect(
115 | listView
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:112:5
|
[chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items:
test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L270
3) [chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items
TimeoutError: locator.click: Timeout 10000ms exceeded.
=========================== logs ===========================
waiting for getByRole('treegrid', { name: 'Block navigation structure' }).getByRole('button', { name: 'Options for Submenu' })
============================================================
268 |
269 | // Open the options menu.
> 270 | await submenuOptions.click();
| ^
271 |
272 | // usage of `page` is required because the options menu is rendered into a slot
273 | // outside of the treegrid.
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:270:24
|
[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:
test/e2e/specs/editor/blocks/navigation.spec.js#L34
4) [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
|
[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:
test/e2e/specs/editor/blocks/navigation.spec.js#L69
5) [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
|
[chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu:
test/e2e/specs/editor/blocks/navigation.spec.js#L197
6) [chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu
TimeoutError: locator.click: Timeout 10000ms exceeded.
=========================== logs ===========================
waiting for frameLocator('[name="editor-canvas"]').getByRole('button', { name: 'Add block' })
============================================================
195 | name: 'Add block',
196 | } );
> 197 | await navBlockInserter.click();
| ^
198 |
199 | await page.keyboard.type( 'https://example.com' );
200 | await page.keyboard.press( 'Enter' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:197:27
|
[chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu:
test/e2e/specs/editor/blocks/navigation.spec.js#L197
6) [chromium] › editor/blocks/navigation.spec.js:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
TimeoutError: locator.click: Timeout 10000ms exceeded.
=========================== logs ===========================
waiting for frameLocator('[name="editor-canvas"]').getByRole('button', { name: 'Add block' })
============================================================
195 | name: 'Add block',
196 | } );
> 197 | await navBlockInserter.click();
| ^
198 |
199 | await page.keyboard.type( 'https://example.com' );
200 | await page.keyboard.press( 'Enter' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation.spec.js:197:27
|
Playwright - 2
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
Puppeteer
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/.
|
Playwright - 8
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/.
|
Playwright - 5
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/.
|
Playwright - 1
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/.
|
Playwright - 3
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/.
|
Playwright - 7
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/.
|
Playwright - 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/.
|
Playwright - 4
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/.
|
Playwright - 2
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/.
|
Report to GitHub
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/.
|
🎭 Playwright Run Summary
3 skipped
129 passed (7.8m)
|
🎭 Playwright Run Summary
1 skipped
158 passed (7.9m)
|
🎭 Playwright Run Summary
11 skipped
152 passed (8.0m)
|
🎭 Playwright Run Summary
163 passed (8.2m)
|
🎭 Playwright Run Summary
189 passed (8.0m)
|
🎭 Playwright Run Summary
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 (8.2m)
|
🎭 Playwright Run Summary
162 passed (8.6m)
|
🎭 Playwright Run Summary
6 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-list-view.spec.js:86:2 › Navigation block - List view editing › list view should correctly reflect navigation items' structure
[chromium] › editor/blocks/navigation-list-view.spec.js:253:2 › Navigation block - List view editing › can remove menu items
[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
[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:180:3 › Navigation block › As a user I want to create submenus using the navigation block › create a submenu
1 skipped
153 passed (9.8m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
failures-artifacts
Expired
|
277 KB |
|
flaky-tests-report
Expired
|
948 Bytes |
|