1) [Chrome] › read-receipts/new-messages-thread-roots.spec.ts:38:17 › Read receipts › new messages › thread roots › Reading a thread root within the thread view marks it as read in the main timeline @mergequeue Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByRole('treeitem', { name: /^Room Beta/ }).locator('.mx_NotificationBadge_count') Expected string: "23" Received string: "61" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByRole('treeitem', { name: /^Room Beta/ }).locator('.mx_NotificationBadge_count') 9 × locator resolved to <span class="mx_NotificationBadge_count">61</span> - unexpected value "61" at read-receipts/index.ts:473 471 | await expect(tile.locator(".mx_NotificationBadge_dot")).toBeVisible(); 472 | } else { > 473 | await expect(tile.locator(".mx_NotificationBadge_count")).toHaveText(count.toString()); | ^ 474 | } 475 | } 476 | at Helpers.assertUnread (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:473:71) at /home/runner/work/element-web/element-web/playwright/e2e/read-receipts/new-messages-thread-roots.spec.ts:61:28

1) [Chrome] › read-receipts/editing-messages-in-threads.spec.ts:44:17 › Read receipts › editing messages › in threads › Reading an edit of a threaded message makes the room read @mergequeue Test timeout of 30000ms exceeded.

1) [Chrome] › read-receipts/editing-messages-in-threads.spec.ts:44:17 › Read receipts › editing messages › in threads › Reading an edit of a threaded message makes the room read @mergequeue Error: jsHandle.evaluateHandle: Test timeout of 30000ms exceeded. at read-receipts/index.ts:88 86 | } 87 | > 88 | const promise = room.evaluateHandle( | ^ 89 | async (room, { message, includeThreads }) => { 90 | let ev = room.timeline.find((e) => e.getContent().body === message); 91 | if (!ev && includeThreads) { at MessageBuilder.getMessage (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:88:30) at MessageContentSpec.getContent (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:187:53) at Helpers.sendMessageAsClient (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:348:61) at Helpers.receiveMessages (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:585:9) at /home/runner/work/element-web/element-web/playwright/e2e/read-receipts/editing-messages-in-threads.spec.ts:52:17

[Chrome] › read-receipts/high-level.spec.ts took 3.1m

[Chrome] › read-receipts/new-messages-in-threads.spec.ts took 1.1m

[Chrome] › read-receipts/new-messages-main-timeline.spec.ts took 44.0s

[Chrome] › read-receipts/redactions-in-threads.spec.ts took 1.5m

[Chrome] › read-receipts/redactions-main-timeline.spec.ts took 1.1m

[Chrome] › read-receipts/reactions-in-threads.spec.ts took 48.9s

[Chrome] › read-receipts/read-receipts.spec.ts took 46.5s

[Chrome] › read-receipts/redactions-thread-roots.spec.ts took 30.6s

[Chrome] › timeline/timeline.spec.ts took 1.4m

[Chrome] › login/login-consent.spec.ts took 1.1m

[Chrome] › crypto/backups-mas.spec.ts took 36.0s

[Chrome] › threads/threads.spec.ts took 32.3s

[Chrome] › crypto/event-shields.spec.ts took 53.6s

[Chrome] › audio-player/audio-player.spec.ts took 38.1s

[Chrome] › composer/RTE.spec.ts took 36.8s

[Chrome] › crypto/crypto.spec.ts took 34.9s

[Chrome] › crypto/decryption-failure-messages.spec.ts took 29.3s

[Chrome] › messages/messages.spec.ts took 59.9s

[Chrome] › pinned-messages/pinned-messages.spec.ts took 58.9s

[Chrome] › read-receipts/editing-messages-main-timeline.spec.ts took 39.5s

[Chrome] › read-receipts/editing-messages-thread-roots.spec.ts took 31.0s

[Chrome] › invite/invite-dialog.spec.ts took 25.5s

[Chrome] › spotlight/spotlight.spec.ts took 2.2m

[Chrome] › sliding-sync/sliding-sync.spec.ts took 58.6s

[Chrome] › spaces/threads-activity-centre/threadsActivityCentre.spec.ts took 48.2s

[Chrome] › spaces/spaces.spec.ts took 31.1s

[Chrome] › settings/encryption-user-tab/recovery.spec.ts took 30.0s

1 flaky [Chrome] › read-receipts/new-messages-thread-roots.spec.ts:38:17 › Read receipts › new messages › thread roots › Reading a thread root within the thread view marks it as read in the main timeline @mergequeue 43 skipped 32 passed (6.2m)

2 skipped 75 passed (6.6m)

5 skipped 63 passed (6.4m)

82 passed (6.7m)

1 flaky [Chrome] › read-receipts/editing-messages-in-threads.spec.ts:44:17 › Read receipts › editing messages › in threads › Reading an edit of a threaded message makes the room read @mergequeue 2 skipped 78 passed (6.9m)