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

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

1) [chromium] › specs/editor/blocks/comments.spec.js:177:2 › Comments › The editable block version is rendered if the legacy attribute is false Error: apiRequestContext.fetch: socket hang up Call log: - → GET http://localhost:8889/wp-json/wp/v2/users/me - user-agent: Playwright/1.58.2 (x64; ubuntu 24.04) node/20.20 CI/1 - accept: */* - accept-encoding: gzip,deflate,br - X-WP-Nonce: 5d81c920d8 - cookie: wordpress_test_cookie=WP%20Cookie%20check; wordpress_logged_in_23778236db82f19306f247e20a353a99=admin%7C1775781659%7CoH8oqWsW1FvSsOEbQs2JeXM25JjtE4xv8wHE1l71sEj%7C941e9251aaad87c0d70cf31e2be922ce058b229f7424cc447acc78d8f502ff30; wp-settings-time-1=1775609042 at ../../../packages/e2e-test-utils-playwright/src/request-utils/rest.ts:119 117 | 118 | try { > 119 | const response = await this.request.fetch( url, { | ^ 120 | ...fetchOptions, 121 | failOnStatusCode: false, 122 | headers: { at RequestUtils.rest (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/rest.ts:119:39) at RequestUtils.createComment (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/comments.ts:32:33) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/comments.spec.js:188:22

Process completed with exit code 1.

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

No artifacts found matching pattern 'blob-reports--*'

No artifacts found matching pattern 'failures-artifacts*'

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 243 passed (12.0m)

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 231 passed (12.5m)

1 skipped 240 passed (12.7m)

3 skipped 242 passed (12.8m)

1 flaky [chromium] › specs/editor/blocks/comments.spec.js:177:2 › Comments › The editable block version is rendered if the legacy attribute is false 245 passed (13.1m)

5 skipped 238 passed (17.9m)

6 skipped 242 passed (14.4m)