Editor: Fix 'useHideBlocksFromInserter' hook filename #97299
Annotations
4 errors, 1 warning, and 1 notice
Run the tests:
test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L270
1) [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
|
Run the tests:
test/e2e/specs/editor/blocks/navigation.spec.js#L114
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
|
Run the tests:
test/e2e/specs/editor/blocks/navigation.spec.js#L114
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
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
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
|
Run the tests:
test/e2e/specs/editor/blocks/navigation.spec.js#L197
3) [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
|
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/.
|
Run the tests
3 flaky
[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: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
[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
159 passed (8.5m)
|
The logs for this run have expired and are no longer available.
Loading