1) [Chrome] › read-receipts/redactions-in-threads.spec.ts:410:17 › Read receipts › redactions › in threads › A thread with a redacted unread is still read after restart Error: Timed out 5000ms waiting for expect(locator).not.toBeVisible() Locator: getByRole('treeitem', { name: /^Room Beta/ }).locator('.mx_NotificationBadge_dot') Expected: not visible Received: visible Call log: - expect.not.toBeVisible with timeout 5000ms - waiting for getByRole('treeitem', { name: /^Room Beta/ }).locator('.mx_NotificationBadge_dot') 9 × locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge_visible mx_NotificationBadge_dot">…</div> - unexpected value "visible" at read-receipts/index.ts:446 444 | async assertRead(room: string | { name: string }) { 445 | const tile = this.getRoomListTile(room); > 446 | await expect(tile.locator(".mx_NotificationBadge_dot")).not.toBeVisible(); | ^ 447 | await expect(tile.locator(".mx_NotificationBadge_count")).not.toBeVisible(); 448 | } 449 | at Helpers.assertRead (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:446:69) at /home/runner/work/element-web/element-web/playwright/e2e/read-receipts/redactions-in-threads.spec.ts:440:28

2) [Chrome] › read-receipts/redactions-thread-roots.spec.ts:136:17 › Read receipts › redactions › thread roots › Editing a redacted thread root leaves the room read Error: jsHandle.evaluate: TypeError: Cannot read properties of undefined (reading 'roomId') at eval (eval at evaluate (:234:30), <anonymous>:1:14) at UtilityScript.evaluate (<anonymous>:236:17) at UtilityScript.<anonymous> (<anonymous>:1:44) at eval (/home/runner/work/element-web/element-web/eval at evaluate (:234:30), <anonymous>:1:14) at UtilityScript.evaluate (/home/runner/work/element-web/element-web/<anonymous>:236:17) at UtilityScript.<anonymous> (/home/runner/work/element-web/element-web/<anonymous>:1:44) at Helpers.sendMessageAsClient (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:338:35) at Helpers.receiveMessages (/home/runner/work/element-web/element-web/playwright/e2e/read-receipts/index.ts:582:9) at /home/runner/work/element-web/element-web/playwright/e2e/read-receipts/redactions-thread-roots.spec.ts:144:17

1) [Chrome] › crypto/decryption-failure-messages.spec.ts:31:13 › Cryptography › decryption failure messages › should handle device-relative historical messages Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: locator('.mx_EventTile').nth(2) Expected string: "test2 test2" Received string: "14:20Unable to decrypt message" Call log: - expect.toContainText with timeout 5000ms - waiting for locator('.mx_EventTile').nth(2) 9 × locator resolved to <li tabindex="-1" aria-live="off" data-self="true" aria-atomic="true" data-layout="group" data-has-reply="false" data-event-id="$wTgyJosAVl450SSm6Acp3F_58Dm2Esj9Y7C87quoFqw" data-scroll-tokens="$wTgyJosAVl450SSm6Acp3F_58Dm2Esj9Y7C87quoFqw" class="mx_EventTile mx_EventTile_continuation mx_EventTile_last mx_EventTile_lastInSection mx_EventTile_bad">…</li> - unexpected value "14:20Unable to decrypt message" 89 | 90 | // The second message should now be decrypted, with a grey shield > 91 | await expect(tilesAfterVerify[1]).toContainText("test2 test2"); | ^ 92 | await expect(tilesAfterVerify[1].locator(".mx_EventTile_e2eIcon_normal")).toBeVisible(); 93 | }); 94 | at /home/runner/work/element-web/element-web/playwright/e2e/crypto/decryption-failure-messages.spec.ts:91:47

1) [Chrome] › crypto/decryption-failure-messages.spec.ts:31:13 › Cryptography › decryption failure messages › should handle device-relative historical messages Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: locator('.mx_EventTile').nth(2) Expected string: "test2 test2" Received string: "14:20Unable to decrypt message" Call log: - expect.toContainText with timeout 5000ms - waiting for locator('.mx_EventTile').nth(2) 9 × locator resolved to <li tabindex="-1" aria-live="off" data-self="true" aria-atomic="true" data-layout="group" data-has-reply="false" data-event-id="$T6_QvfhveWYJuRodvJS1Uxzseo3057X96xH4MqEziB8" data-scroll-tokens="$T6_QvfhveWYJuRodvJS1Uxzseo3057X96xH4MqEziB8" class="mx_EventTile mx_EventTile_continuation mx_EventTile_last mx_EventTile_lastInSection mx_EventTile_bad">…</li> - unexpected value "14:20Unable to decrypt message" 89 | 90 | // The second message should now be decrypted, with a grey shield > 91 | await expect(tilesAfterVerify[1]).toContainText("test2 test2"); | ^ 92 | await expect(tilesAfterVerify[1].locator(".mx_EventTile_e2eIcon_normal")).toBeVisible(); 93 | }); 94 | at /home/runner/work/element-web/element-web/playwright/e2e/crypto/decryption-failure-messages.spec.ts:91:47

1) [Chrome] › crypto/decryption-failure-messages.spec.ts:31:13 › Cryptography › decryption failure messages › should handle device-relative historical messages Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toContainText(expected) Locator: locator('.mx_EventTile').nth(2) Expected string: "test2 test2" Received string: "14:21Unable to decrypt message" Call log: - expect.toContainText with timeout 5000ms - waiting for locator('.mx_EventTile').nth(2) 9 × locator resolved to <li tabindex="-1" aria-live="off" data-self="true" aria-atomic="true" data-layout="group" data-has-reply="false" data-event-id="$Q5IXTGXn0oEjHkm44ELdwLqV2LFCAGsdn-xGPR_-Oiw" data-scroll-tokens="$Q5IXTGXn0oEjHkm44ELdwLqV2LFCAGsdn-xGPR_-Oiw" class="mx_EventTile mx_EventTile_continuation mx_EventTile_last mx_EventTile_lastInSection mx_EventTile_bad">…</li> - unexpected value "14:21Unable to decrypt message" 89 | 90 | // The second message should now be decrypted, with a grey shield > 91 | await expect(tilesAfterVerify[1]).toContainText("test2 test2"); | ^ 92 | await expect(tilesAfterVerify[1].locator(".mx_EventTile_e2eIcon_normal")).toBeVisible(); 93 | }); 94 | at /home/runner/work/element-web/element-web/playwright/e2e/crypto/decryption-failure-messages.spec.ts:91:47

2) [Chrome] › crypto/logout.spec.ts:17:9 › Logout tests › Ask to set up recovery on logout if not setup Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) 28 | await expect( 29 | currentDialogLocator.getByRole("heading", { name: "You'll lose access to your encrypted messages" }), > 30 | ).toBeVisible(); | ^ 31 | }); 32 | 33 | test("If backup is set up show standard confirm", async ({ page, app }) => { at /home/runner/work/element-web/element-web/playwright/e2e/crypto/logout.spec.ts:30:11

2) [Chrome] › crypto/logout.spec.ts:17:9 › Logout tests › Ask to set up recovery on logout if not setup Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) 28 | await expect( 29 | currentDialogLocator.getByRole("heading", { name: "You'll lose access to your encrypted messages" }), > 30 | ).toBeVisible(); | ^ 31 | }); 32 | 33 | test("If backup is set up show standard confirm", async ({ page, app }) => { at /home/runner/work/element-web/element-web/playwright/e2e/crypto/logout.spec.ts:30:11

2) [Chrome] › crypto/logout.spec.ts:17:9 › Logout tests › Ask to set up recovery on logout if not setup Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) Expected: visible Received: <element(s) not found> Call log: - expect.toBeVisible with timeout 5000ms - waiting for locator('.mx_Dialog').getByRole('heading', { name: 'You\'ll lose access to your encrypted messages' }) 28 | await expect( 29 | currentDialogLocator.getByRole("heading", { name: "You'll lose access to your encrypted messages" }), > 30 | ).toBeVisible(); | ^ 31 | }); 32 | 33 | test("If backup is set up show standard confirm", async ({ page, app }) => { at /home/runner/work/element-web/element-web/playwright/e2e/crypto/logout.spec.ts:30:11

Process completed with exit code 1.

1) [Chrome] › pinned-messages/pinned-messages.spec.ts:129:9 › Pinned messages › should display 4 messages in the banner @screenshot Error: expect(locator).toHaveScreenshot(expected) 436 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/element-web/element-web/playwright/snapshots/pinned-messages/pinned-messages.spec.ts/pinned-message-banner-4-Msg4-linux.png Received: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome/pinned-message-banner-4-Msg4-actual.png Diff: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome/pinned-message-banner-4-Msg4-diff.png Call log: - expect.toHaveScreenshot(pinned-message-banner-4-Msg4.png) with timeout 5000ms - verifying given screenshot expectation - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 436 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 436 pixels (ratio 0.01 of all image pixels) are different. 134 | for (const msg of ["Msg4", "Msg3", "Msg2", "Msg1"]) { 135 | await util.assertMessageInBanner(msg); > 136 | await expect(util.getBanner()).toMatchScreenshot(`pinned-message-banner-4-${msg}.png`); | ^ 137 | await util.getBanner().click(); 138 | } 139 | }); at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:136:44

1) [Chrome] › pinned-messages/pinned-messages.spec.ts:129:9 › Pinned messages › should display 4 messages in the banner @screenshot Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveScreenshot(expected) 436 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/element-web/element-web/playwright/snapshots/pinned-messages/pinned-messages.spec.ts/pinned-message-banner-4-Msg4-linux.png Received: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome-retry1/pinned-message-banner-4-Msg4-actual.png Diff: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome-retry1/pinned-message-banner-4-Msg4-diff.png Call log: - expect.toHaveScreenshot(pinned-message-banner-4-Msg4.png) with timeout 5000ms - verifying given screenshot expectation - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 436 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 436 pixels (ratio 0.01 of all image pixels) are different. 134 | for (const msg of ["Msg4", "Msg3", "Msg2", "Msg1"]) { 135 | await util.assertMessageInBanner(msg); > 136 | await expect(util.getBanner()).toMatchScreenshot(`pinned-message-banner-4-${msg}.png`); | ^ 137 | await util.getBanner().click(); 138 | } 139 | }); at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:136:44

1) [Chrome] › pinned-messages/pinned-messages.spec.ts:129:9 › Pinned messages › should display 4 messages in the banner @screenshot Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toHaveScreenshot(expected) 436 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/element-web/element-web/playwright/snapshots/pinned-messages/pinned-messages.spec.ts/pinned-message-banner-4-Msg4-linux.png Received: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome-retry2/pinned-message-banner-4-Msg4-actual.png Diff: /home/runner/work/element-web/element-web/playwright/test-results/pinned-messages-pinned-mes-6cce3-ay-4-messages-in-the-banner-Chrome-retry2/pinned-message-banner-4-Msg4-diff.png Call log: - expect.toHaveScreenshot(pinned-message-banner-4-Msg4.png) with timeout 5000ms - verifying given screenshot expectation - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - 436 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for getByTestId('pinned-message-banner') - locator resolved to <div data-single-message="false" class="mx_PinnedMessageBanner" data-testid="pinned-message-banner" aria-label="This room has pinned messages. Click to view them.">…</div> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - 436 pixels (ratio 0.01 of all image pixels) are different. 134 | for (const msg of ["Msg4", "Msg3", "Msg2", "Msg1"]) { 135 | await util.assertMessageInBanner(msg); > 136 | await expect(util.getBanner()).toMatchScreenshot(`pinned-message-banner-4-${msg}.png`); | ^ 137 | await util.getBanner().click(); 138 | } 139 | }); at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:136:44

2) [Chrome] › oidc/oidc-native.spec.ts:21:9 › OIDC Native › can register the oauth2 client and an account Test timeout of 90000ms exceeded.

2) [Chrome] › oidc/oidc-native.spec.ts:21:9 › OIDC Native › can register the oauth2 client and an account Error: page.waitForRequest: Test timeout of 90000ms exceeded. 21 | test("can register the oauth2 client and an account", async ({ context, page, homeserver, mailhog, mas }) => { 22 | const tokenUri = `http://localhost:${mas.port}/oauth2/token`; > 23 | const tokenApiPromise = page.waitForRequest( | ^ 24 | (request) => request.url() === tokenUri && request.postDataJSON()["grant_type"] === "authorization_code", 25 | ); 26 | at /home/runner/work/element-web/element-web/playwright/e2e/oidc/oidc-native.spec.ts:23:38

3) [Chrome] › pinned-messages/pinned-messages.spec.ts:55:9 › Pinned messages › should pin messages and show them in the pinned message panel Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: locator('#mx_RightPanel').getByRole('heading', { name: 'Pinned messages' }) Expected string: "3 Pinned messages" Received string: "2 Pinned messages" Call log: - expect.toHaveText with timeout 5000ms - waiting for locator('#mx_RightPanel').getByRole('heading', { name: 'Pinned messages' }) 9 × locator resolved to <p role="heading" class="_typography_yh5dq_162 _font-body-md-medium_yh5dq_69 mx_BaseCard_header_title_heading">2 Pinned messages</p> - unexpected value "2 Pinned messages" at pinned-messages/index.ts:182 180 | async assertPinnedMessagesList(messages: string[]) { 181 | const rightPanel = this.getRightPanel(); > 182 | await expect(rightPanel.getByRole("heading", { name: "Pinned messages" })).toHaveText( | ^ 183 | `${messages.length} Pinned messages`, 184 | ); 185 | at Helpers.assertPinnedMessagesList (/home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/index.ts:182:84) at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:63:20

4) [Chrome] › pinned-messages/pinned-messages.spec.ts:66:9 › Pinned messages › should unpin one message Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: locator('#mx_RightPanel').getByRole('heading', { name: 'Pinned messages' }) Expected string: "2 Pinned messages" Received: <element(s) not found> Call log: - expect.toHaveText with timeout 5000ms - waiting for locator('#mx_RightPanel').getByRole('heading', { name: 'Pinned messages' }) at pinned-messages/index.ts:182 180 | async assertPinnedMessagesList(messages: string[]) { 181 | const rightPanel = this.getRightPanel(); > 182 | await expect(rightPanel.getByRole("heading", { name: "Pinned messages" })).toHaveText( | ^ 183 | `${messages.length} Pinned messages`, 184 | ); 185 | at Helpers.assertPinnedMessagesList (/home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/index.ts:182:84) at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:74:20

5) [Chrome] › pinned-messages/pinned-messages.spec.ts:141:9 › Pinned messages › should open the pinned messages list from the banner Test timeout of 30000ms exceeded.

5) [Chrome] › pinned-messages/pinned-messages.spec.ts:141:9 › Pinned messages › should open the pinned messages list from the banner Error: locator.click: Test timeout of 30000ms exceeded. Call log: - waiting for getByRole('button', { name: 'View all' }) 144 | await util.pinMessages(["Msg1", "Msg2"]); 145 | > 146 | await util.getViewAllButton().click(); | ^ 147 | await util.assertPinnedMessagesList(["Msg1", "Msg2"]); 148 | 149 | await expect(util.getCloseListButton()).toBeVisible(); at /home/runner/work/element-web/element-web/playwright/e2e/pinned-messages/pinned-messages.spec.ts:146:39

5) [Chrome] › pinned-messages/pinned-messages.spec.ts:141:9 › Pinned messages › should open the pinned messages list from the banner Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

Stale screenshot file

Stale screenshot file

Stale screenshot file

Stale screenshot file

Process completed with exit code 1.

[Chrome] › spaces/spaces.spec.ts took 1.0m

[Chrome] › right-panel/right-panel.spec.ts took 56.6s

[Chrome] › settings/account-user-settings-tab.spec.ts took 45.5s

[Chrome] › right-panel/file-panel.spec.ts took 39.6s

[Chrome] › settings/appearance-user-settings-tab/theme-choice-panel.spec.ts took 32.7s

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

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

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

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

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

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

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

[Chrome] › spaces/threads-activity-centre/threadsActivityCentre.spec.ts took 1.7m

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

[Chrome] › user-onboarding/user-onboarding-new.spec.ts took 35.2s

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

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

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

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

[Chrome] › read-receipts/reactions-main-timeline.spec.ts took 36.4s

[Chrome] › composer/RTE.spec.ts took 1.3m

[Chrome] › audio-player/audio-player.spec.ts took 1.2m

[Chrome] › crypto/event-shields.spec.ts took 1.2m

[Chrome] › crypto/crypto.spec.ts took 1.1m

[Chrome] › crypto/device-verification.spec.ts took 45.0s

[Chrome] › messages/messages.spec.ts took 2.4m

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

[Chrome] › knock/knock-into-room.spec.ts took 39.5s

[Chrome] › polls/polls.spec.ts took 36.1s

[Chrome] › integration-manager/read_events.spec.ts took 35.9s

9 skipped 68 passed (9.2m)

32 skipped 50 passed (9.9m)

3 skipped 69 passed (10.2m)

2 flaky [Chrome] › read-receipts/redactions-in-threads.spec.ts:410:17 › Read receipts › redactions › in threads › A thread with a redacted unread is still read after restart [Chrome] › read-receipts/redactions-thread-roots.spec.ts:136:17 › Read receipts › redactions › thread roots › Editing a redacted thread root leaves the room read 15 skipped 58 passed (10.5m)

2 failed [Chrome] › crypto/decryption-failure-messages.spec.ts:31:13 › Cryptography › decryption failure messages › should handle device-relative historical messages [Chrome] › crypto/logout.spec.ts:17:9 › Logout tests › Ask to set up recovery on logout if not setup 77 passed (13.7m)