1) [Chrome] › playwright/e2e/read-receipts/new-messages-main-timeline.spec.ts:53:13 › Read receipts › new messages › in the main timeline › Reading an older message leaves the room unread @mergequeue Error: expect(received).toBeLessThan(expected) Expected: < 30 Received: 30 Call Log: - Timeout 5000ms exceeded while waiting on the predicate at read-receipts/index.ts:493 491 | // https://playwright.dev/docs/test-assertions#expectpoll 492 | // .toBeLessThan doesn't have a retry mechanism, so we use .poll > 493 | await expect | ^ 494 | .poll(async () => { 495 | return this.unreadCountForRoomTile(tile); 496 | }) at Helpers.assertUnreadLessThan (/home/runner/work/element-web/element-web/apps/web/playwright/e2e/read-receipts/index.ts:493:9) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/read-receipts/new-messages-main-timeline.spec.ts:68:17

1) [Chrome] › playwright/e2e/editing/editing.spec.ts:306:5 › Editing › should correctly display events which are edited, where we lack the edit event Error: expect(locator).toHaveText(expected) failed Locator: locator('[data-event-id="$vAOtt5QH42tzGPU9HhmKBM8Uk_sVSOc-HbFyQRVUF0U"]').locator('.mx_EventTile_body') Expected: "Edited body" Timeout: 5000ms Error: element(s) not found Call log: - Expect "toHaveText" with timeout 5000ms - waiting for locator('[data-event-id="$vAOtt5QH42tzGPU9HhmKBM8Uk_sVSOc-HbFyQRVUF0U"]').locator('.mx_EventTile_body') 369 | 370 | // nevertheless, the event should be updated > 371 | await expect(messageTile.locator(".mx_EventTile_body")).toHaveText("Edited body"); | ^ 372 | await expect(messageTile.locator(".mx_EventTile_edited")).toBeVisible(); 373 | }); 374 | }); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/editing/editing.spec.ts:371:65

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, nbucic/variable-mapper@0673f6891a0619ba7c002ecfed0f9f4f39017b6f. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

1 skipped 6 passed (21.3s)

1 skipped 6 passed (21.2s)

1 skipped 6 passed (15.1s)

1 skipped 6 passed (20.1s)

1 flaky [Chrome] › playwright/e2e/read-receipts/new-messages-main-timeline.spec.ts:53:13 › Read receipts › new messages › in the main timeline › Reading an older message leaves the room unread @mergequeue 33 skipped 123 passed (12.9m)

1 skipped 6 passed (23.1s)

15 skipped 158 passed (14.1m)

2 skipped 167 passed (18.0m)

1 flaky [Chrome] › playwright/e2e/editing/editing.spec.ts:306:5 › Editing › should correctly display events which are edited, where we lack the edit event 185 passed (18.3m)

1 skipped 6 passed (23.2s)

1 skipped 6 passed (29.5s)