try animate frame #97002
Annotations
2 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#L69
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
|
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
2 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: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.7m)
|
The logs for this run have expired and are no longer available.
Loading