Skip to content

Enqueue block custom CSS only when block renders on the page. #96945

Enqueue block custom CSS only when block renders on the page.

Enqueue block custom CSS only when block renders on the page. #96945

Triggered via pull request February 14, 2024 02:15
Status Success
Total duration 19m 31s
Artifacts 2

end2end-test.yml

on: pull_request
Matrix: e2e-playwright
Report to GitHub
3m 39s
Report to GitHub
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 10 warnings, and 8 notices
[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.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
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
[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
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
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 - 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 - 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 - 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 - 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 - 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 - 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 - 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.6m)
🎭 Playwright Run Summary
4 skipped 157 passed (7.9m)
🎭 Playwright Run Summary
11 skipped 152 passed (8.0m)
🎭 Playwright Run Summary
189 passed (8.1m)
🎭 Playwright Run Summary
1 skipped 162 passed (8.2m)
🎭 Playwright Run Summary
162 passed (8.7m)
🎭 Playwright Run Summary
165 passed (8.4m)
🎭 Playwright Run Summary
3 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.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 158 passed (8.9m)

Artifacts

Produced during runtime
Name Size
failures-artifacts Expired
3.82 MB
flaky-tests-report Expired
3.57 KB