1) [chromium] › interactivity/directive-each.spec.ts:21:6 › data-wp-each › should use `item` as the defaul item name in the context SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON at ../../../packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104 102 | }, 103 | } ); > 104 | const json: RestResponse = await response.json(); | ^ 105 | 106 | if ( ! response.ok() ) { 107 | throw json; at RequestUtils.rest (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104:30) at RequestUtils.createPost (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/posts.ts:64:15) at InteractivityUtils.addPostWithBlock (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/fixtures/interactivity-utils.ts:58:20) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-each.spec.ts:9:3

1) [chromium] › interactivity/directive-each.spec.ts:21:6 › data-wp-each › should use `item` as the defaul item name in the context Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON at ../../../packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104 102 | }, 103 | } ); > 104 | const json: RestResponse = await response.json(); | ^ 105 | 106 | if ( ! response.ok() ) { 107 | throw json; at RequestUtils.rest (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104:30) at RequestUtils.createPost (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/posts.ts:64:15) at InteractivityUtils.addPostWithBlock (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/fixtures/interactivity-utils.ts:58:20) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-each.spec.ts:9:3

1) [chromium] › interactivity/directive-each.spec.ts:21:6 › data-wp-each › should use `item` as the defaul item name in the context Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON at ../../../packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104 102 | }, 103 | } ); > 104 | const json: RestResponse = await response.json(); | ^ 105 | 106 | if ( ! response.ok() ) { 107 | throw json; at RequestUtils.rest (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/rest.ts:104:30) at RequestUtils.createPost (/home/runner/work/gutenberg/gutenberg/packages/e2e-test-utils-playwright/src/request-utils/posts.ts:64:15) at InteractivityUtils.addPostWithBlock (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/fixtures/interactivity-utils.ts:58:20) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-each.spec.ts:9:3

2) [chromium] › interactivity/directive-on-window.spec.ts:21:6 › data-wp-on-window › callbacks should run whenever the specified event is dispatched Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('counter') Expected string: "1" Received string: "0" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('counter') - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" - locator resolved to <p data-testid="counter" data-wp-text="state.counte…>0</p> - unexpected value "0" 24 | await page.setViewportSize( { width: 600, height: 600 } ); 25 | const counter = page.getByTestId( 'counter' ); > 26 | await expect( counter ).toHaveText( '1' ); | ^ 27 | } ); 28 | test( 'the event listener is removed when the element is removed', async ( { 29 | page, at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-on-window.spec.ts:26:27

Process completed with exit code 1.

158 passed (7.8m)

1 skipped 147 passed (8.0m)

11 skipped 150 passed (7.8m)

3 skipped 119 passed (7.6m)

1 skipped 143 passed (7.2m)

4 skipped 120 passed (6.2m)

168 passed (7.6m)

1 failed [chromium] › interactivity/directive-each.spec.ts:21:6 › data-wp-each › should use `item` as the defaul item name in the context 1 flaky [chromium] › interactivity/directive-on-window.spec.ts:21:6 › data-wp-on-window › callbacks should run whenever the specified event is dispatched 17 skipped 159 passed (7.3m)

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.