Skip to content

ValidatedRangeControl: Fix aria-label rendered as [object Object] #150495

ValidatedRangeControl: Fix aria-label rendered as [object Object]

ValidatedRangeControl: Fix aria-label rendered as [object Object] #150495

Triggered via pull request April 6, 2026 11:50
Status Success
Total duration 29m 50s
Artifacts 1

end2end-test.yml

on: pull_request
Matrix: e2e-playwright
Merge Artifacts
38s
Merge Artifacts
Report to GitHub
1m 42s
Report to GitHub
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 8 notices
[chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page: test/e2e/specs/site-editor/homepage-settings.spec.js#L93
1) [chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page Error: locator.click: Error: strict mode violation: getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') }) resolved to 2 elements: 1) <div class="" id=":ru:" role="row">…</div> aka getByRole('row', { name: 'Sample Page Edit Actions Author Author avatar admin Status Published', exact: true }) 2) <div class="" id=":r16:" role="row">…</div> aka getByRole('row', { name: 'Sample page Edit Actions Author Author avatar admin Status Published', exact: true }) Call log: - waiting for getByRole('row').filter({ has: getByRole('gridcell').getByLabel('Sample page') }) 91 | .filter( { has: samplePageTwo } ); 92 | // eslint-disable-next-line playwright/no-force-option > 93 | await samplePageTwoRow.click( { force: true } ); | ^ 94 | await samplePageTwoRow 95 | .getByRole( 'button', { 96 | name: 'Actions', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/homepage-settings.spec.js:93:26
[chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted: packages/e2e-test-utils-playwright/src/editor/select-blocks.ts#L26
1) [chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted › Paragraph and Group blocks are available in the inserter TimeoutError: locator.getAttribute: Timeout 10000ms exceeded. Call log: - waiting for locator('[name="editor-canvas"]').contentFrame().getByText('Initial content') at ../../../packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26 24 | : endSelectorOrLocator; 25 | > 26 | const startClientId = await startBlock.getAttribute( 'data-block' ); | ^ 27 | const endClientId = await endBlock?.getAttribute( 'data-block' ); 28 | 29 | if ( endClientId ) { at Editor.selectBlocks (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/editor/select-blocks.ts:26:41) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:163:18 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/post-content-focus-mode.spec.js:159:15
[chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks: test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L615
1) [chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks › Save post and verify migration was written to database Error: expect(received).toContain(expected) // indexOf Expected substring: "\"submenuVisibility\":\"click\"" Received string: "<!-- wp:navigation {\"openSubmenusOnClick\":true,\"overlayMenu\":\"never\"} --> <!-- wp:navigation-submenu {\"label\":\"Products\"} --> <!-- wp:navigation-link {\"label\":\"Product 1\",\"url\":\"#\"} /--> <!-- wp:navigation-link {\"label\":\"Product 2\",\"url\":\"#\"} /--> <!-- /wp:navigation-submenu --> <!-- wp:navigation-link {\"label\":\"About\",\"url\":\"#\"} /--> <!-- /wp:navigation -->" 613 | const content = savedPost.content.raw; 614 | > 615 | expect( content ).toContain( '"submenuVisibility":"click"' ); | ^ 616 | expect( content ).not.toContain( 'openSubmenusOnClick' ); 617 | } ); 618 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:615:23 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:593:4
Merge Artifacts
Process completed with exit code 1.
Merge Artifacts
Unable to download artifact(s): Artifact not found for name: blob-reports-merged Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Merge Artifacts
No artifacts found matching pattern 'blob-reports--*'
Merge Artifacts
No artifacts found matching pattern 'failures-artifacts*'
🎭 Playwright Run Summary
1 flaky [chromium] › specs/site-editor/homepage-settings.spec.js:62:2 › Homepage Settings via Editor › should show correct homepage actions based on current homepage or posts page 3 skipped 242 passed (9.4m)
🎭 Playwright Run Summary
1 skipped 239 passed (13.0m)
🎭 Playwright Run Summary
1 flaky [chromium] › specs/editor/various/post-content-focus-mode.spec.js:129:3 › Post Content focus mode › post content inside a template part › post title and content are editable and blocks can be inserted 5 skipped 230 passed (13.1m)
🎭 Playwright Run Summary
3 skipped 242 passed (13.1m)
🎭 Playwright Run Summary
246 passed (13.2m)
🎭 Playwright Run Summary
6 skipped 237 passed (14.0m)
🎭 Playwright Run Summary
5 skipped 238 passed (15.9m)
🎭 Playwright Run Summary
1 flaky [chromium] › specs/editor/blocks/navigation-frontend-interactivity.spec.js:528:3 › Navigation block - Frontend interactivity › Legacy openSubmenusOnClick backward compatibility › Should render and migrate legacy openSubmenusOnClick blocks 1 skipped 258 passed (23.9m)

Artifacts

Produced during runtime
Name Size Digest
flaky-tests-report
3.39 KB
sha256:b6d9bc57696eb29ca499b19e3d78f9bbbaae8f9ef8855f7ae31abed6a79ece8e