1) [Chrome] › playwright/e2e/read-receipts/redactions-in-threads.spec.ts:61:13 › Read receipts › redactions › in threads › Reading an unread thread after a redaction of the latest message makes it read @mergequeue Error: expect(locator).not.toBeVisible() failed Locator: locator('.mx_ThreadPanel li').filter({ hasText: 'Root' }).locator('.mx_NotificationBadge') Expected: not visible Received: visible Timeout: 5000ms Call log: - Expect "not toBeVisible" with timeout 5000ms - waiting for locator('.mx_ThreadPanel li').filter({ hasText: 'Root' }).locator('.mx_NotificationBadge') 9 × locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge_visible mx_NotificationBadge_level_notification mx_NotificationBadge_dot">…</div> - unexpected value "visible" at read-receipts/index.ts:560 558 | async assertReadThread(rootMessage: string) { 559 | const tile = await this.getThreadListTile(rootMessage); > 560 | await expect(tile.locator(".mx_NotificationBadge")).not.toBeVisible(); | ^ 561 | } 562 | 563 | /** at Helpers.assertReadThread (/home/runner/work/element-web/element-web/apps/web/playwright/e2e/read-receipts/index.ts:560:65) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/read-receipts/redactions-in-threads.spec.ts:89:17

1) [Chrome] › playwright/e2e/crypto/toasts.spec.ts:45:5 › Key storage out of sync toast › should prompt for recovery key if 'enter recovery key' pressed @screenshot Error: expect(locator).toHaveScreenshot(expected) failed Locator: getByRole('alert').first() Timeout: 5000ms Timeout 5000ms exceeded. Snapshot: key-storage-out-of-sync-toast.png Call log: - Expect "toHaveScreenshot(key-storage-out-of-sync-toast.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for getByRole('alert').first() - locator resolved to <div role="alert" class="mx_NonUrgentToastContainer"></div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action 2 × waiting for element to be stable - element is not visible - retrying scroll into view action - waiting 20ms 2 × waiting for element to be stable - element is not visible - retrying scroll into view action - waiting 100ms 9 × waiting for element to be stable - element is not visible - retrying scroll into view action - waiting 500ms - Timeout 5000ms exceeded. 48 | // it would always be checking the same toast, even if another one is now the first. 49 | await expect(page.getByRole("alert")).toHaveCount(2); > 50 | await expect(page.getByRole("alert").first()).toMatchScreenshot( | ^ 51 | "key-storage-out-of-sync-toast.png", 52 | screenshotOptions, 53 | ); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/crypto/toasts.spec.ts:50:55

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Eun/http-server-action@f71cec1321f665652a46c40b6852f8e5a68bfcd4. 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: cardinalby/git-get-release-action@5172c3a026600b1d459b117738c605fabc9e4e44. 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: 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/

16 passed (2.1m)

1 flaky [Chrome] › playwright/e2e/read-receipts/redactions-in-threads.spec.ts:61:13 › Read receipts › redactions › in threads › Reading an unread thread after a redaction of the latest message makes it read @mergequeue 3 skipped 161 passed (14.9m)

1 flaky [Chrome] › playwright/e2e/crypto/toasts.spec.ts:45:5 › Key storage out of sync toast › should prompt for recovery key if 'enter recovery key' pressed @screenshot 167 passed (17.2m)

45 skipped 125 passed (12.8m)

2 skipped 163 passed (17.8m)

1 skipped 6 passed (21.8s)

1 skipped 6 passed (19.2s)

1 skipped 6 passed (31.4s)

1 skipped 6 passed (18.8s)

1 skipped 6 passed (26.6s)

1 skipped 6 passed (26.4s)

1 skipped 6 passed (28.2s)