1) [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array TimeoutError: locator.evaluate: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByTestId('second-item') ============================================================ 29 | const id = await page 30 | .getByTestId( 'second-item' ) > 31 | .evaluate( ( n ) => ( n as any )._id ); | ^ 32 | expect( id ).toBe( 123 ); 33 | } ); 34 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-key.spec.ts:31:5

1) [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.evaluate: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByTestId('second-item') ============================================================ 29 | const id = await page 30 | .getByTestId( 'second-item' ) > 31 | .evaluate( ( n ) => ( n as any )._id ); | ^ 32 | expect( id ).toBe( 123 ); 33 | } ); 34 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-key.spec.ts:31:5

1) [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.evaluate: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByTestId('second-item') ============================================================ 29 | const id = await page 30 | .getByTestId( 'second-item' ) > 31 | .evaluate( ( n ) => ( n as any )._id ); | ^ 32 | expect( id ).toBe( 123 ); 33 | } ); 34 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-key.spec.ts:31:5

2) [chromium] › interactivity/directives-context.spec.ts:166:6 › data-wp-context › should replace values on navigation Error: expect(received).toHaveText(expected) Expected string: "second page" Received string: "first page" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" 170 | await expect( element ).toHaveText( 'changed dynamically' ); 171 | await page.getByTestId( 'navigate' ).click(); > 172 | await expect( element ).toHaveText( 'second page' ); | ^ 173 | } ); 174 | 175 | test( 'should preserve the previous context values', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:172:27

2) [chromium] › interactivity/directives-context.spec.ts:166:6 › data-wp-context › should replace values on navigation Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveText(expected) Expected string: "second page" Received string: "first page" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" 170 | await expect( element ).toHaveText( 'changed dynamically' ); 171 | await page.getByTestId( 'navigate' ).click(); > 172 | await expect( element ).toHaveText( 'second page' ); | ^ 173 | } ); 174 | 175 | test( 'should preserve the previous context values', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:172:27

2) [chromium] › interactivity/directives-context.spec.ts:166:6 › data-wp-context › should replace values on navigation Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveText(expected) Expected string: "second page" Received string: "first page" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - waiting for getByTestId('navigation text') - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" - locator resolved to <div data-wp-text="context.text" data-testid="navigat…>first page</div> - unexpected value "first page" 170 | await expect( element ).toHaveText( 'changed dynamically' ); 171 | await page.getByTestId( 'navigate' ).click(); > 172 | await expect( element ).toHaveText( 'second page' ); | ^ 173 | } ); 174 | 175 | test( 'should preserve the previous context values', async ( { page } ) => { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:172:27

3) [chromium] › interactivity/directives-context.spec.ts:175:6 › data-wp-context › should preserve the previous context values Error: expect(received).toHaveText(expected) Expected string: "some new text" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" 179 | await expect( element ).toHaveText( 'some new text' ); 180 | await page.getByTestId( 'navigate' ).click(); > 181 | await expect( element ).toHaveText( 'some new text' ); | ^ 182 | } ); 183 | 184 | test( 'should maintain the same context reference on async actions', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:181:27

3) [chromium] › interactivity/directives-context.spec.ts:175:6 › data-wp-context › should preserve the previous context values Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveText(expected) Expected string: "some new text" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" 179 | await expect( element ).toHaveText( 'some new text' ); 180 | await page.getByTestId( 'navigate' ).click(); > 181 | await expect( element ).toHaveText( 'some new text' ); | ^ 182 | } ); 183 | 184 | test( 'should maintain the same context reference on async actions', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:181:27

3) [chromium] › interactivity/directives-context.spec.ts:175:6 › data-wp-context › should preserve the previous context values Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveText(expected) Expected string: "some new text" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" 179 | await expect( element ).toHaveText( 'some new text' ); 180 | await page.getByTestId( 'navigate' ).click(); > 181 | await expect( element ).toHaveText( 'some new text' ); | ^ 182 | } ); 183 | 184 | test( 'should maintain the same context reference on async actions', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:181:27

4) [chromium] › interactivity/directives-context.spec.ts:184:6 › data-wp-context › should maintain the same context reference on async actions Error: expect(received).toHaveText(expected) Expected string: "changed from async action" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - waiting for getByTestId('navigation new text') - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" - locator resolved to <div data-wp-text="context.newText" data-testid="navi…></div> - unexpected value "" 188 | await expect( element ).toHaveText( '' ); 189 | await page.getByTestId( 'async navigate' ).click(); > 190 | await expect( element ).toHaveText( 'changed from async action' ); | ^ 191 | } ); 192 | } ); 193 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-context.spec.ts:190:27

1) [webkit] › editor/various/multi-block-selection.spec.js:1169:2 › Multi-block selection › should partially select with shift + click (@WebKit) Error: expect(received).toMatchObject(expected) - Expected - 1 + Received + 1 Array [ Object { "attributes": Object { - "content": "<strong>1</strong>|2", + "content": "|", }, "name": "core/paragraph", }, ] Call Log: - Timeout 5000ms exceeded while waiting on the predicate 1210 | // Ensure selection is in the correct place. 1211 | await page.keyboard.type( '|' ); > 1212 | await expect.poll( editor.getBlocks ).toMatchObject( [ | ^ 1213 | { 1214 | name: 'core/paragraph', 1215 | attributes: { content: '<strong>1</strong>|2' }, at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/multi-block-selection.spec.js:1212:3

4 failed [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array [chromium] › interactivity/directives-context.spec.ts:166:6 › data-wp-context › should replace values on navigation [chromium] › interactivity/directives-context.spec.ts:175:6 › data-wp-context › should preserve the previous context values [chromium] › interactivity/directives-context.spec.ts:184:6 › data-wp-context › should maintain the same context reference on async actions 1 skipped 218 passed (18.7m)

253 passed (21.1m)

11 skipped 227 passed (19.8m)