2) [chromium] › test/e2e/specs/editor/various/content-only-lock.spec.js:80:2 › Content-only lock › should be able to automatically stop temporarily modify as blocks when an outside block is selected Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeAttached() failed Locator: locator('.color-block-support-panel') Expected: attached Received: <element(s) not found> Timeout: 5000ms Call log: - Expect "toBeAttached" with timeout 5000ms - waiting for locator('.color-block-support-panel') 116 | await expect( 117 | page.locator( '.color-block-support-panel' ) > 118 | ).toBeAttached(); | ^ 119 | await editor.clickBlockOptionsMenuItem( 'Delete' ); 120 | // Select an outside block 121 | await editor.canvas at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/content-only-lock.spec.js:118:5

2) [chromium] › test/e2e/specs/editor/various/content-only-lock.spec.js:80:2 › Content-only lock › should be able to automatically stop temporarily modify as blocks when an outside block is selected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeAttached() failed Locator: locator('.color-block-support-panel') Expected: attached Received: <element(s) not found> Timeout: 5000ms Call log: - Expect "toBeAttached" with timeout 5000ms - waiting for locator('.color-block-support-panel') 116 | await expect( 117 | page.locator( '.color-block-support-panel' ) > 118 | ).toBeAttached(); | ^ 119 | await editor.clickBlockOptionsMenuItem( 'Delete' ); 120 | // Select an outside block 121 | await editor.canvas at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/content-only-lock.spec.js:118:5

2) [chromium] › test/e2e/specs/editor/various/content-only-lock.spec.js:80:2 › Content-only lock › should be able to automatically stop temporarily modify as blocks when an outside block is selected Error: expect(locator).toBeAttached() failed Locator: locator('.color-block-support-panel') Expected: attached Received: <element(s) not found> Timeout: 5000ms Call log: - Expect "toBeAttached" with timeout 5000ms - waiting for locator('.color-block-support-panel') 116 | await expect( 117 | page.locator( '.color-block-support-panel' ) > 118 | ).toBeAttached(); | ^ 119 | await editor.clickBlockOptionsMenuItem( 'Delete' ); 120 | // Select an outside block 121 | await editor.canvas at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/content-only-lock.spec.js:118:5

[chromium] › test/e2e/specs/editor/various/color-support.spec.js:11:6 › Link color in themes › should apply selected link color in editor and frontend: test/e2e/specs/editor/various/color-support.spec.js#L72

1) [chromium] › test/e2e/specs/editor/various/color-support.spec.js:11:6 › Link color in themes › should apply selected link color in editor and frontend Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveCSS(expected) failed Locator: getByRole('link', { name: 'custom link color set' }) Expected string: "rgb(255, 0, 0)" Received string: "rgb(40, 48, 61)" Timeout: 5000ms Call log: - Expect "toHaveCSS" with timeout 5000ms - waiting for getByRole('link', { name: 'custom link color set' }) 9 × locator resolved to <a href="https://example.com">custom link color set</a> - unexpected value "rgb(40, 48, 61)" 70 | * #ff0000 is rgb(255, 0, 0). 71 | */ > 72 | await expect( previewContent ).toHaveCSS( 'color', 'rgb(255, 0, 0)' ); | ^ 73 | } ); 74 | } ); 75 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/color-support.spec.js:72:34

1) [chromium] › test/e2e/specs/editor/various/color-support.spec.js:11:6 › Link color in themes › should apply selected link color in editor and frontend Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveCSS(expected) failed Locator: getByRole('link', { name: 'custom link color set' }) Expected string: "rgb(255, 0, 0)" Received string: "rgb(40, 48, 61)" Timeout: 5000ms Call log: - Expect "toHaveCSS" with timeout 5000ms - waiting for getByRole('link', { name: 'custom link color set' }) 9 × locator resolved to <a href="https://example.com">custom link color set</a> - unexpected value "rgb(40, 48, 61)" 70 | * #ff0000 is rgb(255, 0, 0). 71 | */ > 72 | await expect( previewContent ).toHaveCSS( 'color', 'rgb(255, 0, 0)' ); | ^ 73 | } ); 74 | } ); 75 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/color-support.spec.js:72:34

1) [chromium] › test/e2e/specs/editor/various/color-support.spec.js:11:6 › Link color in themes › should apply selected link color in editor and frontend Error: expect(locator).toHaveCSS(expected) failed Locator: getByRole('link', { name: 'custom link color set' }) Expected string: "rgb(255, 0, 0)" Received string: "rgb(40, 48, 61)" Timeout: 5000ms Call log: - Expect "toHaveCSS" with timeout 5000ms - waiting for getByRole('link', { name: 'custom link color set' }) 9 × locator resolved to <a href="https://example.com">custom link color set</a> - unexpected value "rgb(40, 48, 61)" 70 | * #ff0000 is rgb(255, 0, 0). 71 | */ > 72 | await expect( previewContent ).toHaveCSS( 'color', 'rgb(255, 0, 0)' ); | ^ 73 | } ); 74 | } ); 75 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/color-support.spec.js:72:34

Playwright - 4

Process completed with exit code 1.

[chromium] › test/e2e/specs/editor/various/list-view.spec.js:337:2 › List View › ensures List View global shortcut works properly: test/e2e/specs/editor/various/list-view.spec.js#L419

3) [chromium] › test/e2e/specs/editor/various/list-view.spec.js:337:2 › List View › ensures List View global shortcut works properly Error: expect(locator).toBeFocused() failed Locator: getByRole('region', { name: 'Document Overview' }).getByRole('button', { name: 'Close' }) Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for getByRole('region', { name: 'Document Overview' }).getByRole('button', { name: 'Close' }) 9 × locator resolved to <button type="button" aria-label="Close" class="components-button block-editor-tabbed-sidebar__close-button is-compact has-icon">…</button> - unexpected value "inactive" 417 | name: 'Close', 418 | } ) > 419 | ).toBeFocused(); | ^ 420 | 421 | // Close List View and ensure it's closed. 422 | await pageUtils.pressKeys( 'access+o' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/list-view.spec.js:419:5

[chromium] › test/e2e/specs/editor/various/patterns.spec.js:208:2 › Synced pattern › can be saved when modified inside of a published post: test/e2e/specs/editor/various/patterns.spec.js#L266

2) [chromium] › test/e2e/specs/editor/various/patterns.spec.js:208:2 › Synced pattern › can be saved when modified inside of a published post Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: locator('#reused-paragraph') Expected string: "Einen Guten Tag!" Received string: "Guten Tag!" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for locator('#reused-paragraph') 9 × locator resolved to <p id="reused-paragraph">Guten Tag!</p> - unexpected value "Guten Tag!" 264 | // Check that the frontend shows the updated content. 265 | await page.goto( `/?p=${ postId }` ); > 266 | await expect( page.locator( '#reused-paragraph' ) ).toHaveText( | ^ 267 | 'Einen Guten Tag!' 268 | ); 269 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/patterns.spec.js:266:55

2) [chromium] › test/e2e/specs/editor/various/patterns.spec.js:208:2 › Synced pattern › can be saved when modified inside of a published post Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: locator('#reused-paragraph') Expected string: "Einen Guten Tag!" Received string: "Guten Tag!" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for locator('#reused-paragraph') 9 × locator resolved to <p id="reused-paragraph">Guten Tag!</p> - unexpected value "Guten Tag!" 264 | // Check that the frontend shows the updated content. 265 | await page.goto( `/?p=${ postId }` ); > 266 | await expect( page.locator( '#reused-paragraph' ) ).toHaveText( | ^ 267 | 'Einen Guten Tag!' 268 | ); 269 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/patterns.spec.js:266:55

2) [chromium] › test/e2e/specs/editor/various/patterns.spec.js:208:2 › Synced pattern › can be saved when modified inside of a published post Error: expect(locator).toHaveText(expected) failed Locator: locator('#reused-paragraph') Expected string: "Einen Guten Tag!" Received string: "Guten Tag!" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for locator('#reused-paragraph') 9 × locator resolved to <p id="reused-paragraph">Guten Tag!</p> - unexpected value "Guten Tag!" 264 | // Check that the frontend shows the updated content. 265 | await page.goto( `/?p=${ postId }` ); > 266 | await expect( page.locator( '#reused-paragraph' ) ).toHaveText( | ^ 267 | 'Einen Guten Tag!' 268 | ); 269 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/patterns.spec.js:266:55

[chromium] › test/e2e/specs/editor/various/draggable-blocks.spec.js:332:2 › Draggable block › can drag and drop to an empty parent block like Group or Columns: test/e2e/specs/editor/various/draggable-blocks.spec.js#L398

1) [chromium] › test/e2e/specs/editor/various/draggable-blocks.spec.js:332:2 › Draggable block › can drag and drop to an empty parent block like Group or Columns Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Dragging over the button block appender should show the blue background expect(locator).toHaveCSS(expected) failed Locator: locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) Expected string: "rgb(0, 124, 186)" Received string: "rgb(56, 88, 233)" Timeout: 5000ms Call log: - Dragging over the button block appender should show the blue background with timeout 5000ms - waiting for locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) 9 × locator resolved to <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" class="components-button block-editor-button-block-appender is-next-40px-default-size">…</button> - unexpected value "rgb(56, 88, 233)" 396 | rowAppender, 397 | 'Dragging over the button block appender should show the blue background' > 398 | ).toHaveCSS( 'background-color', 'rgb(0, 124, 186)' ); | ^ 399 | 400 | const { width: rowWidth } = await rowBlock.boundingBox(); 401 | await dragOver( rowBlock, { position: { x: rowWidth - 10 } } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/draggable-blocks.spec.js:398:6

1) [chromium] › test/e2e/specs/editor/various/draggable-blocks.spec.js:332:2 › Draggable block › can drag and drop to an empty parent block like Group or Columns Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Dragging over the button block appender should show the blue background expect(locator).toHaveCSS(expected) failed Locator: locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) Expected string: "rgb(0, 124, 186)" Received string: "rgb(56, 88, 233)" Timeout: 5000ms Call log: - Dragging over the button block appender should show the blue background with timeout 5000ms - waiting for locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) 9 × locator resolved to <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" class="components-button block-editor-button-block-appender is-next-40px-default-size">…</button> - unexpected value "rgb(56, 88, 233)" 396 | rowAppender, 397 | 'Dragging over the button block appender should show the blue background' > 398 | ).toHaveCSS( 'background-color', 'rgb(0, 124, 186)' ); | ^ 399 | 400 | const { width: rowWidth } = await rowBlock.boundingBox(); 401 | await dragOver( rowBlock, { position: { x: rowWidth - 10 } } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/draggable-blocks.spec.js:398:6

1) [chromium] › test/e2e/specs/editor/various/draggable-blocks.spec.js:332:2 › Draggable block › can drag and drop to an empty parent block like Group or Columns Error: Dragging over the button block appender should show the blue background expect(locator).toHaveCSS(expected) failed Locator: locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) Expected string: "rgb(0, 124, 186)" Received string: "rgb(56, 88, 233)" Timeout: 5000ms Call log: - Dragging over the button block appender should show the blue background with timeout 5000ms - waiting for locator('[name="editor-canvas"]').contentFrame().getByRole('document', { name: 'Block: Row' }).getByRole('button', { name: 'Add block' }) 9 × locator resolved to <button type="button" aria-haspopup="true" aria-expanded="false" aria-label="Add block" class="components-button block-editor-button-block-appender is-next-40px-default-size">…</button> - unexpected value "rgb(56, 88, 233)" 396 | rowAppender, 397 | 'Dragging over the button block appender should show the blue background' > 398 | ).toHaveCSS( 'background-color', 'rgb(0, 124, 186)' ); | ^ 399 | 400 | const { width: rowWidth } = await rowBlock.boundingBox(); 401 | await dragOver( rowBlock, { position: { x: rowWidth - 10 } } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/draggable-blocks.spec.js:398:6

Playwright - 1

Process completed with exit code 1.

[chromium] › test/e2e/specs/editor/blocks/navigation-list-view.spec.js:134:2 › Navigation block - List view editing › can add new menu items: test/e2e/specs/editor/blocks/navigation-list-view.spec.js#L191

1) [chromium] › test/e2e/specs/editor/blocks/navigation-list-view.spec.js:134:2 › Navigation block - List view editing › can add new menu items Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() Expected string: "Page Link" Received string: "Page link" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() 9 × locator resolved to <button id=":r2n:" tabindex="0" type="button" role="option" data-active-item="true" class="components-button block-editor-block-types-list__item editor-block-list-item-navigation-link/page is-next-40px-default-size">…</button> - unexpected value "Page link" 189 | // Expect to see the Page Link and Custom Link blocks as the nth(0) and nth(1) results. 190 | // This is important for usability as the Page Link block is the most likely to be used. > 191 | await expect( blockResultOptions.nth( 0 ) ).toHaveText( 'Page Link' ); | ^ 192 | await expect( blockResultOptions.nth( 1 ) ).toHaveText( 'Custom Link' ); 193 | 194 | // Select the Page Link option. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:191:47

1) [chromium] › test/e2e/specs/editor/blocks/navigation-list-view.spec.js:134:2 › Navigation block - List view editing › can add new menu items Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() Expected string: "Page Link" Received string: "Page link" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() 9 × locator resolved to <button id=":r2n:" tabindex="0" type="button" role="option" data-active-item="true" class="components-button block-editor-block-types-list__item editor-block-list-item-navigation-link/page is-next-40px-default-size">…</button> - unexpected value "Page link" 189 | // Expect to see the Page Link and Custom Link blocks as the nth(0) and nth(1) results. 190 | // This is important for usability as the Page Link block is the most likely to be used. > 191 | await expect( blockResultOptions.nth( 0 ) ).toHaveText( 'Page Link' ); | ^ 192 | await expect( blockResultOptions.nth( 1 ) ).toHaveText( 'Custom Link' ); 193 | 194 | // Select the Page Link option. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:191:47

1) [chromium] › test/e2e/specs/editor/blocks/navigation-list-view.spec.js:134:2 › Navigation block - List view editing › can add new menu items Error: expect(locator).toHaveText(expected) failed Locator: getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() Expected string: "Page Link" Received string: "Page link" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByRole('listbox', { name: 'Blocks' }).getByRole('option').first() 9 × locator resolved to <button id=":r2n:" tabindex="0" type="button" role="option" data-active-item="true" class="components-button block-editor-block-types-list__item editor-block-list-item-navigation-link/page is-next-40px-default-size">…</button> - unexpected value "Page link" 189 | // Expect to see the Page Link and Custom Link blocks as the nth(0) and nth(1) results. 190 | // This is important for usability as the Page Link block is the most likely to be used. > 191 | await expect( blockResultOptions.nth( 0 ) ).toHaveText( 'Page Link' ); | ^ 192 | await expect( blockResultOptions.nth( 1 ) ).toHaveText( 'Custom Link' ); 193 | 194 | // Select the Page Link option. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-list-view.spec.js:191:47

[chromium] › test/e2e/specs/site-editor/command-center.spec.js:76:2 › Site editor command palette › Open the command palette and navigate to a template: test/e2e/specs/site-editor/command-center.spec.js#L83

4) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:76:2 › Site editor command palette › Open the command palette and navigate to a template TimeoutError: locator.click: Timeout 10000ms exceeded. Call log: - waiting for getByRole('option', { name: 'index' }) 81 | .click(); 82 | await page.keyboard.type( 'index' ); > 83 | await page.getByRole( 'option', { name: 'index' } ).click(); | ^ 84 | await expect( 85 | page 86 | .getByRole( 'region', { name: 'Editor top bar' } ) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:83:55

[chromium] › test/e2e/specs/site-editor/command-center.spec.js:63:2 › Site editor command palette › Open the command palette and create post using "create" keyword: test/e2e/specs/site-editor/command-center.spec.js#L71

3) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:63:2 › Site editor command palette › Open the command palette and create post using "create" keyword Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 69 | await page 70 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 71 | .fill( 'create' ); | ^ 72 | await page.getByRole( 'option', { name: 'Add Post' } ).click(); 73 | await expect( page ).toHaveURL( /\/wp-admin\/post-new\.php/ ); 74 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:71:5

3) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:63:2 › Site editor command palette › Open the command palette and create post using "create" keyword Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 69 | await page 70 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 71 | .fill( 'create' ); | ^ 72 | await page.getByRole( 'option', { name: 'Add Post' } ).click(); 73 | await expect( page ).toHaveURL( /\/wp-admin\/post-new\.php/ ); 74 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:71:5

3) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:63:2 › Site editor command palette › Open the command palette and create post using "create" keyword TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 69 | await page 70 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 71 | .fill( 'create' ); | ^ 72 | await page.getByRole( 'option', { name: 'Add Post' } ).click(); 73 | await expect( page ).toHaveURL( /\/wp-admin\/post-new\.php/ ); 74 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:71:5

[chromium] › test/e2e/specs/site-editor/command-center.spec.js:43:2 › Site editor command palette › Open the command palette and create page using "create" keyword: test/e2e/specs/site-editor/command-center.spec.js#L51

2) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:43:2 › Site editor command palette › Open the command palette and create page using "create" keyword Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 49 | await page 50 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 51 | .fill( 'create' ); | ^ 52 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 53 | await expect( page ).toHaveURL( 54 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:51:5

2) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:43:2 › Site editor command palette › Open the command palette and create page using "create" keyword Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 49 | await page 50 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 51 | .fill( 'create' ); | ^ 52 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 53 | await expect( page ).toHaveURL( 54 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:51:5

2) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:43:2 › Site editor command palette › Open the command palette and create page using "create" keyword TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 49 | await page 50 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 51 | .fill( 'create' ); | ^ 52 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 53 | await expect( page ).toHaveURL( 54 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:51:5

[chromium] › test/e2e/specs/site-editor/command-center.spec.js:23:2 › Site editor command palette › Open the command palette and navigate to the page create page: test/e2e/specs/site-editor/command-center.spec.js#L31

1) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:23:2 › Site editor command palette › Open the command palette and navigate to the page create page Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 29 | await page 30 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 31 | .fill( 'new' ); | ^ 32 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 33 | await expect( page ).toHaveURL( 34 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:31:5

1) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:23:2 › Site editor command palette › Open the command palette and navigate to the page create page Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 29 | await page 30 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 31 | .fill( 'new' ); | ^ 32 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 33 | await expect( page ).toHaveURL( 34 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:31:5

1) [chromium] › test/e2e/specs/site-editor/command-center.spec.js:23:2 › Site editor command palette › Open the command palette and navigate to the page create page TimeoutError: locator.fill: Timeout 10000ms exceeded. Call log: - waiting for getByRole('combobox', { name: 'Search commands and settings' }) 29 | await page 30 | .getByRole( 'combobox', { name: 'Search commands and settings' } ) > 31 | .fill( 'new' ); | ^ 32 | await page.getByRole( 'option', { name: 'Add Page' } ).click(); 33 | await expect( page ).toHaveURL( 34 | /\/wp-admin\/site-editor.php\?p=%2Fpage%2F(\d+)&canvas=edit/ at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/site-editor/command-center.spec.js:31:5

[chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:221:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content in editor and respect changes made there: test/e2e/specs/editor/plugins/block-hooks.spec.js#L273

4) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:221:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content in editor and respect changes made there Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 1 + Received + 1 Array [ - "hooked-block-last_child-post-content", + "hooked-block-last_child-post-content wp-block-paragraph", "dummy-heading", "dummy-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 3 elements 271 | await expect( 272 | page.locator( '.entry-content > *' ) > 273 | ).toHaveClass( [ | ^ 274 | getHookedBlockClassName( 'last_child', blockType ), 275 | 'dummy-heading', 276 | 'dummy-paragraph', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:273:7

[chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content on frontend: test/e2e/specs/editor/plugins/block-hooks.spec.js#L214

3) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content on frontend Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 1 + Received + 1 Array [ "dummy-heading", "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 3 elements 212 | await expect( 213 | page.locator( '.entry-content > *' ) > 214 | ).toHaveClass( [ | ^ 215 | 'dummy-heading', 216 | 'dummy-paragraph', 217 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:214:7

3) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content on frontend Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 1 + Received + 1 Array [ "dummy-heading", "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 3 elements 212 | await expect( 213 | page.locator( '.entry-content > *' ) > 214 | ).toHaveClass( [ | ^ 215 | 'dummy-heading', 216 | 'dummy-paragraph', 217 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:214:7

3) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content on frontend Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 1 + Received + 1 Array [ "dummy-heading", "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 3 elements 212 | await expect( 213 | page.locator( '.entry-content > *' ) > 214 | ).toHaveClass( [ | ^ 215 | 'dummy-heading', 216 | 'dummy-paragraph', 217 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:214:7

[chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content in editor and respect changes made there: test/e2e/specs/editor/plugins/block-hooks.spec.js#L159

2) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content in editor and respect changes made there Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "hooked-block-last_child-post-content", - "dummy-paragraph", + "hooked-block-after-heading wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 157 | await expect( 158 | page.locator( '.entry-content > *' ) > 159 | ).toHaveClass( [ | ^ 160 | 'wp-block-heading', 161 | getHookedBlockClassName( 'after', 'core/heading' ), 162 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:159:7

2) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content in editor and respect changes made there Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "hooked-block-last_child-post-content", - "dummy-paragraph", + "hooked-block-after-heading wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 157 | await expect( 158 | page.locator( '.entry-content > *' ) > 159 | ).toHaveClass( [ | ^ 160 | 'wp-block-heading', 161 | getHookedBlockClassName( 'after', 'core/heading' ), 162 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:159:7

2) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content in editor and respect changes made there Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "hooked-block-last_child-post-content", - "dummy-paragraph", + "hooked-block-after-heading wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 157 | await expect( 158 | page.locator( '.entry-content > *' ) > 159 | ).toHaveClass( [ | ^ 160 | 'wp-block-heading', 161 | getHookedBlockClassName( 'after', 'core/heading' ), 162 | getHookedBlockClassName( 'last_child', blockType ), at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:159:7

[chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content on frontend: test/e2e/specs/editor/plugins/block-hooks.spec.js#L85

1) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content on frontend Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-after-heading wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 83 | await expect( 84 | page.locator( '.entry-content > *' ) > 85 | ).toHaveClass( [ | ^ 86 | 'wp-block-heading', 87 | getHookedBlockClassName( 'after', 'core/heading' ), 88 | 'dummy-paragraph', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:85:7

1) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content on frontend Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-after-heading wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 83 | await expect( 84 | page.locator( '.entry-content > *' ) > 85 | ).toHaveClass( [ | ^ 86 | 'wp-block-heading', 87 | getHookedBlockClassName( 'after', 'core/heading' ), 88 | 'dummy-paragraph', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:85:7

1) [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content on frontend Error: expect(locator).toHaveClass(expected) failed Locator: locator('.entry-content > *') - Expected - 3 + Received + 3 Array [ "wp-block-heading", - "hooked-block-after-heading", - "dummy-paragraph", - "hooked-block-last_child-post-content", + "hooked-block-after-heading wp-block-paragraph", + "dummy-paragraph wp-block-paragraph", + "hooked-block-last_child-post-content wp-block-paragraph", ] Timeout: 5000ms Call log: - Expect "toHaveClass" with timeout 5000ms - waiting for locator('.entry-content > *') 9 × locator resolved to 4 elements 83 | await expect( 84 | page.locator( '.entry-content > *' ) > 85 | ).toHaveClass( [ | ^ 86 | 'wp-block-heading', 87 | getHookedBlockClassName( 'after', 'core/heading' ), 88 | 'dummy-paragraph', at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/plugins/block-hooks.spec.js:85:7

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected and don't leak up (parent): test/e2e/specs/interactivity/directive-context.spec.ts#L11

4) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected and don't leak up (parent) SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:82:24

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected and don't leak down (child): test/e2e/specs/interactivity/directive-context.spec.ts#L11

3) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected and don't leak down (child) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:61:24

3) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected and don't leak down (child) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:61:24

3) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected and don't leak down (child) SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:61:24

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow): test/e2e/specs/interactivity/directive-context.spec.ts#L11

2) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:42:24

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow): test/e2e/specs/interactivity/directive-context.spec.ts#L11

2) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:42:24

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow): test/e2e/specs/interactivity/directive-context.spec.ts#L11

2) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow) SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:42:24

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized: test/e2e/specs/interactivity/directive-context.spec.ts#L11

1) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:29:25

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized: test/e2e/specs/interactivity/directive-context.spec.ts#L11

1) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:29:25

[chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized: test/e2e/specs/interactivity/directive-context.spec.ts#L11

1) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized SyntaxError: Unexpected end of JSON input 9 | 10 | const parseContent = async ( loc: Locator ) => > 11 | JSON.parse( ( await loc.textContent() ) || '' ); | ^ 12 | 13 | test.describe( 'data-wp-context', () => { 14 | test.beforeAll( async ( { interactivityUtils: utils } ) => { at parseContent (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:11:7) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:29:25

[chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:154:6 › getServerContext() › should prevent any manual modifications: test/e2e/specs/interactivity/get-sever-context.spec.ts#L158

4) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:154:6 › getServerContext() › should prevent any manual modifications Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('prop') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('prop') 9 × locator resolved to <div data-testid="prop" data-wp-text="context.prop"></div> - unexpected value "" 156 | const button = page.getByTestId( 'tryToModifyServerContext' ); 157 | > 158 | await expect( prop ).toHaveText( 'child' ); | ^ 159 | await expect( button ).toHaveText( 'modify' ); 160 | 161 | await button.click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:158:24

[chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:136:6 › getServerContext() › should keep new props on navigation: test/e2e/specs/interactivity/get-sever-context.spec.ts#L143

3) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:136:6 › getServerContext() › should keep new props on navigation Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 141 | await page.getByTestId( 'newProps' ).click(); 142 | > 143 | await expect( newProp ).toHaveText( 'child' ); | ^ 144 | await expect( nestedNewProp ).toHaveText( 'child' ); 145 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 146 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:143:27

3) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:136:6 › getServerContext() › should keep new props on navigation Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 141 | await page.getByTestId( 'newProps' ).click(); 142 | > 143 | await expect( newProp ).toHaveText( 'child' ); | ^ 144 | await expect( nestedNewProp ).toHaveText( 'child' ); 145 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 146 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:143:27

3) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:136:6 › getServerContext() › should keep new props on navigation Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 141 | await page.getByTestId( 'newProps' ).click(); 142 | > 143 | await expect( newProp ).toHaveText( 'child' ); | ^ 144 | await expect( nestedNewProp ).toHaveText( 'child' ); 145 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 146 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:143:27

[chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:120:6 › getServerContext() › should add new props on navigation: test/e2e/specs/interactivity/get-sever-context.spec.ts#L131

2) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:120:6 › getServerContext() › should add new props on navigation Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 129 | await page.getByTestId( 'newProps' ).click(); 130 | > 131 | await expect( newProp ).toHaveText( 'child' ); | ^ 132 | await expect( nestedNewProp ).toHaveText( 'child' ); 133 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 134 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:131:27

2) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:120:6 › getServerContext() › should add new props on navigation Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 129 | await page.getByTestId( 'newProps' ).click(); 130 | > 131 | await expect( newProp ).toHaveText( 'child' ); | ^ 132 | await expect( nestedNewProp ).toHaveText( 'child' ); 133 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 134 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:131:27

2) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:120:6 › getServerContext() › should add new props on navigation Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('newProp') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('newProp') 9 × locator resolved to <div data-testid="newProp" data-wp-text="context.newProp"></div> - unexpected value "" 129 | await page.getByTestId( 'newProps' ).click(); 130 | > 131 | await expect( newProp ).toHaveText( 'child' ); | ^ 132 | await expect( nestedNewProp ).toHaveText( 'child' ); 133 | await expect( inheritedNewProp ).toHaveText( 'parent' ); 134 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:131:27

[chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:98:6 › getServerContext() › should update modified props on navigation: test/e2e/specs/interactivity/get-sever-context.spec.ts#L103

1) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:98:6 › getServerContext() › should update modified props on navigation Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('prop') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('prop') 9 × locator resolved to <div data-testid="prop" data-wp-text="context.prop"></div> - unexpected value "" 101 | const inheritedProp = page.getByTestId( 'inherited.prop' ); 102 | > 103 | await expect( prop ).toHaveText( 'child' ); | ^ 104 | await expect( nestedProp ).toHaveText( 'child' ); 105 | await expect( inheritedProp ).toHaveText( 'parent' ); 106 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:103:24

1) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:98:6 › getServerContext() › should update modified props on navigation Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('prop') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('prop') 9 × locator resolved to <div data-testid="prop" data-wp-text="context.prop"></div> - unexpected value "" 101 | const inheritedProp = page.getByTestId( 'inherited.prop' ); 102 | > 103 | await expect( prop ).toHaveText( 'child' ); | ^ 104 | await expect( nestedProp ).toHaveText( 'child' ); 105 | await expect( inheritedProp ).toHaveText( 'parent' ); 106 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:103:24

1) [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:98:6 › getServerContext() › should update modified props on navigation Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('prop') Expected string: "child" Received string: "" Timeout: 5000ms Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('prop') 9 × locator resolved to <div data-testid="prop" data-wp-text="context.prop"></div> - unexpected value "" 101 | const inheritedProp = page.getByTestId( 'inherited.prop' ); 102 | > 103 | await expect( prop ).toHaveText( 'child' ); | ^ 104 | await expect( nestedProp ).toHaveText( 'child' ); 105 | await expect( inheritedProp ).toHaveText( 'parent' ); 106 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/get-sever-context.spec.ts:103:24

Playwright - 3

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@5a3ec84eff668545956fd18022155c47e93e2684, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@65462800fd760344b1a7b4382951275a0abb4808. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Playwright - 4

Playwright - 1

Playwright - 8

Playwright - 5

Playwright - 2

Playwright - 6

Playwright - 7

Merge Artifacts

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/upload-artifact/merge@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

🎭 Playwright Run Summary

2 failed [chromium] › test/e2e/specs/editor/various/color-support.spec.js:11:6 › Link color in themes › should apply selected link color in editor and frontend [chromium] › test/e2e/specs/editor/various/content-only-lock.spec.js:80:2 › Content-only lock › should be able to automatically stop temporarily modify as blocks when an outside block is selected 1 skipped 207 passed (8.9m)

🎭 Playwright Run Summary

2 failed [chromium] › test/e2e/specs/editor/various/draggable-blocks.spec.js:332:2 › Draggable block › can drag and drop to an empty parent block like Group or Columns [chromium] › test/e2e/specs/editor/various/patterns.spec.js:208:2 › Synced pattern › can be saved when modified inside of a published post 1 flaky [chromium] › test/e2e/specs/editor/various/list-view.spec.js:337:2 › List View › ensures List View global shortcut works properly 1 skipped 206 passed (9.5m)

🎭 Playwright Run Summary

1 failed [chromium] › test/e2e/specs/editor/blocks/navigation-list-view.spec.js:134:2 › Navigation block - List view editing › can add new menu items 216 passed (9.8m)

🎭 Playwright Run Summary

3 skipped 189 passed (10.0m)

🎭 Playwright Run Summary

5 failed [chromium] › test/e2e/specs/site-editor/command-center.spec.js:23:2 › Site editor command palette › Open the command palette and navigate to the page create page [chromium] › test/e2e/specs/site-editor/command-center.spec.js:43:2 › Site editor command palette › Open the command palette and create page using "create" keyword [chromium] › test/e2e/specs/site-editor/command-center.spec.js:63:2 › Site editor command palette › Open the command palette and create post using "create" keyword [chromium] › test/e2e/specs/site-editor/command-center.spec.js:76:2 › Site editor command palette › Open the command palette and navigate to a template [chromium] › test/e2e/specs/site-editor/command-center.spec.js:91:2 › Site editor command palette › Open the command palette and navigate to Customize CSS 1 skipped 204 passed (11.7m)

🎭 Playwright Run Summary

10 failed [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content on frontend [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Post Content (blocks) › should insert hooked blocks into Post Content in editor and respect changes made there [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content on frontend [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:221:4 › Block Hooks API › Hooked blocks in Post Content (classic) › should insert hooked blocks into Post Content in editor and respect changes made there [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:79:4 › Block Hooks API › Hooked blocks in Synced Pattern (blocks) › should insert hooked blocks into Synced Pattern on frontend [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:93:4 › Block Hooks API › Hooked blocks in Synced Pattern (blocks) › should insert hooked blocks into Synced Pattern in editor and respect changes made there [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:208:4 › Block Hooks API › Hooked blocks in Synced Pattern (classic) › should insert hooked blocks into Synced Pattern on frontend [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:221:4 › Block Hooks API › Hooked blocks in Synced Pattern (classic) › should insert hooked blocks into Synced Pattern in editor and respect changes made there [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:314:3 › Block Hooks API › Hooked blocks in Navigation Menu › should insert hooked blocks into Navigation Menu on frontend [chromium] › test/e2e/specs/editor/plugins/block-hooks.spec.js:327:3 › Block Hooks API › Hooked blocks in Navigation Menu › should insert hooked blocks into Navigation Menu in editor and respect changes made there 1 skipped 195 passed (12.6m)

🎭 Playwright Run Summary

50 failed [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended (shallow) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected and don't leak down (child) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected and don't leak up (parent) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:118:6 › data-wp-context › changes in shadowed properties do not leak (parent) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:139:6 › data-wp-context › new inherited properties update child contexts [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:160:6 › data-wp-context › Array properties are shadowed [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:173:6 › data-wp-context › overwritten objects don't inherit values (shallow) [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:197:6 › data-wp-context › overwritten objects do not inherit values [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:219:6 › data-wp-context › can be accessed in other directives on the same element [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:233:6 › data-wp-context › should preserve values on navigation [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:242:6 › data-wp-context › should preserve the previous context values [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:251:6 › data-wp-context › should preserve values when navigating back or forward [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:263:6 › data-wp-context › should inherit values on navigation [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:283:6 › data-wp-context › should maintain the same context reference on async actions [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:292:6 › data-wp-context › should bail out if the context is not a default directive [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:305:6 › data-wp-context › references to objects are kept [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:319:6 › data-wp-context › should not subscribe to parent context props if those also exist in child [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:342:6 › data-wp-context › references to the same context object should be preserved [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:349:6 › data-wp-context › references to copied context objects should be preserved [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:359:6 › data-wp-context › objects referenced from the context inherit properties where they are originally defined [chromium] › test/e2e/specs/interactivity/directive-context.spec.ts:384:6 › data-wp-context › properties from other namespaces defined in a parent context are inherited [chromium] › test/e2e/specs/interactivity/directive-each.spec.ts:63:7 › data-wp-each › without `wp-each-key` › should preserve elements on deletion [chromium] › test/e2e/specs/interactivity/directive-each.spec.ts:78:7 › data-wp-each › without `wp-each-key` › should preserve elements on reordering [chromium] › test/e2e/specs/interactivity/directive-each.spec.ts:96:7 › data-wp-each › without `wp-each-key` › should preserve ele

🎭 Playwright Run Summary

36 failed [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:98:6 › getServerContext() › should update modified props on navigation [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:120:6 › getServerContext() › should add new props on navigation [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:136:6 › getServerContext() › should keep new props on navigation [chromium] › test/e2e/specs/interactivity/get-sever-context.spec.ts:154:6 › getServerContext() › should prevent any manual modifications [chromium] › test/e2e/specs/interactivity/get-sever-state.spec.ts:59:6 › getServerState() › should update existing state props on navigation [chromium] › test/e2e/specs/interactivity/get-sever-state.spec.ts:83:6 › getServerState() › should add new state props and keep them on navigation [chromium] › test/e2e/specs/interactivity/get-sever-state.spec.ts:107:6 › getServerState() › should prevent any manual modifications [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:191:6 › Router navigate › should force a page reload when the `clientNavigationDisabled` config is set to true [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:214:6 › Router navigate › should merge the state with the one serialized in the new page [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:239:6 › Router navigate › should not try to overwrite getters with values from the initial data [chromium] › test/e2e/specs/interactivity/router-navigate.spec.ts:261:6 › Router navigate › should force a page reload when navigating to a page with `clientNavigationDisabled` [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:82:6 › Router regions › should be the only part hydrated [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:92:6 › Router regions › should update after navigation [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:110:6 › Router regions › should preserve state across pages [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:126:6 › Router regions › should preserve context across pages [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:142:6 › Router regions › can be nested [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:160:6 › Router regions › Page title is updated 2 [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:174:6 › Router regions › should not take into account regions that are not in the topmost `data-wp-interactive`. [chromium] › test/e2e/specs/interactivity/router-regions.spec.ts:202:6 › Router regions › should support router regions with the `attachTo` property. [chromium] › test/e2e/specs/interactivity/router-script-modules.spec.ts:80:7 › Router script modules › should handle static modules from new blocks [chromium] › test/e2e/specs/interactivity/router-script-modules.spec.ts:80:7 › Router script modules › should handle dynamic modules from new blocks [chromium] › test/e2e/specs/interactivity/router-script-modules.spec.ts:80:7 › Router script modules › should handle static modules from initial page [chromium] › test/e2e/specs/interactivity/router-script-modules.spec.ts:80:7 › Router script modules › should handle dynamic modules from initial page [chromium] › test/e2e/specs/interactivity/router-styles.spec

Artifacts

Produced during runtime

Name	Size	Digest
failures-artifacts	199 MB	`sha256:4926e956f12d389c9bc2b9bc58373fdbc1b46ee8c48fbb8a17ccd1fe0ba7948d`
flaky-tests-report	2.54 KB	`sha256:299d48b211d95589c401fae2ca5c97e0c45d874924e743411aad77973ba350a7`