1) [Legacy Crypto] › room/room.spec.ts:64:9 › Room Directory › should memorize the timeline position when switch Room A -> Room B -> Room A Error: Timed out 5000ms waiting for expect(locator).toBeInViewport() Locator: locator('.mx_MTextBody .mx_EventTile_body').getByText('test0') Expected: in viewport Received: outside viewport Call log: - expect.toBeInViewport with timeout 5000ms - waiting for locator('.mx_MTextBody .mx_EventTile_body').getByText('test0') 98 | // The timeline should display the first message 99 | // The previous position before switching to Room B should be remembered > 100 | await expect(page.locator(".mx_MTextBody .mx_EventTile_body").getByText("test0")).toBeInViewport(); | ^ 101 | }); 102 | }); 103 | at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/room/room.spec.ts:100:91

2) [Legacy Crypto] › timeline/timeline.spec.ts:910:13 › Timeline › message sending › should display a reply chain Error: Screenshot comparison failed: 103 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/snapshots/timeline/timeline.spec.ts/event-tile-reply-chains-bubble-layout-linux.png Received: /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/test-results/timeline-timeline-Timeline-message-sending-should-display-a-reply-chain-Legacy-Crypto/event-tile-reply-chains-bubble-layout-actual.png Diff: /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/test-results/timeline-timeline-Timeline-message-sending-should-display-a-reply-chain-Legacy-Crypto/event-tile-reply-chains-bubble-layout-diff.png Call log: - page._expectScreenshot with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx_EventTile_last') - locator resolved to <li tabindex="-1" aria-live="off" data-self="true" a…>…</li> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - waiting for element to be visible and stable - element is visible and stable - 103 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx_EventTile_last') - locator resolved to <li tabindex="-1" aria-live="off" data-self="true" a…>…</li> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - waiting for element to be visible and stable - element is visible and stable - captured a stable screenshot - 103 pixels (ratio 0.01 of all image pixels) are different. 1015 | 1016 | // Take a snapshot on bubble layout > 1017 | await expect(page.locator(".mx_EventTile_last")).toMatchScreenshot( | ^ 1018 | "event-tile-reply-chains-bubble-layout.png", 1019 | screenshotOptions, 1020 | ); at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/timeline/timeline.spec.ts:1017:62

3) [Rust Crypto] › crypto/verification.spec.ts:245:9 › User verification › can receive a verification request when there is no existing DM Test timeout of 30000ms exceeded.

3) [Rust Crypto] › crypto/verification.spec.ts:245:9 › User verification › can receive a verification request when there is no existing DM Error: jsHandle.evaluateHandle: Test timeout of 30000ms exceeded. 353 | */ 354 | async function awaitVerifier(botVerificationRequest: JSHandle<VerificationRequest>): Promise<JSHandle<Verifier>> { > 355 | return botVerificationRequest.evaluateHandle(async (verificationRequest) => { | ^ 356 | while (!verificationRequest.verifier) { 357 | await new Promise((r) => verificationRequest.once("change" as any, r)); 358 | } at awaitVerifier (/home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/crypto/verification.spec.ts:355:35) at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/crypto/verification.spec.ts:287:35

4) [Rust Crypto] › read-receipts/redactions.spec.ts:691: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') - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" - locator resolved to <div class="mx_NotificationBadge mx_NotificationBadge…>…</div> - unexpected value "visible" at read-receipts/index.ts:462 460 | async assertRead(room: string | { name: string }) { 461 | const tile = this.getRoomListTile(room); > 462 | await expect(tile.locator(".mx_NotificationBadge_dot")).not.toBeVisible(); | ^ 463 | await expect(tile.locator(".mx_NotificationBadge_count")).not.toBeVisible(); 464 | } 465 | at Helpers.assertRead (/home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/read-receipts/index.ts:462:69) at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/read-receipts/redactions.spec.ts:721:28

5) [Rust Crypto] › room/room.spec.ts:64:9 › Room Directory › should memorize the timeline position when switch Room A -> Room B -> Room A Error: Timed out 5000ms waiting for expect(locator).toBeInViewport() Locator: locator('.mx_MTextBody .mx_EventTile_body').getByText('test0') Expected: in viewport Received: outside viewport Call log: - expect.toBeInViewport with timeout 5000ms - waiting for locator('.mx_MTextBody .mx_EventTile_body').getByText('test0') 98 | // The timeline should display the first message 99 | // The previous position before switching to Room B should be remembered > 100 | await expect(page.locator(".mx_MTextBody .mx_EventTile_body").getByText("test0")).toBeInViewport(); | ^ 101 | }); 102 | }); 103 | at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/room/room.spec.ts:100:91

6) [Rust Crypto] › sliding-sync/sliding-sync.spec.ts:259:9 › Sliding Sync › should show a favourite DM only in the favourite sublist Test timeout of 30000ms exceeded while running "beforeEach" hook. 24 | let roomId: string; 25 | > 26 | test.beforeEach(async ({ slidingSyncProxy, page, user, app }) => { | ^ 27 | roomId = await app.client.createRoom({ name: "Test Room" }); 28 | }); 29 | at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/sliding-sync/sliding-sync.spec.ts:26:10

6) [Rust Crypto] › sliding-sync/sliding-sync.spec.ts:259:9 › Sliding Sync › should show a favourite DM only in the favourite sublist Error: jsHandle.evaluate: Test timeout of 30000ms exceeded. at ../pages/client.ts:153 151 | public async createRoom(options: ICreateRoomOpts): Promise<string> { 152 | const client = await this.prepareClient(); > 153 | return await client.evaluate(async (cli, options) => { | ^ 154 | const resp = await cli.createRoom(options); 155 | const roomId = resp.room_id; 156 | if (!cli.getRoom(roomId)) { at Client.createRoom (/home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/pages/client.ts:153:29) at /home/runner/work/matrix-react-sdk/matrix-react-sdk/matrix-react-sdk/playwright/e2e/sliding-sync/sliding-sync.spec.ts:27:18

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: Sibz/github-status-action@071b5370da85afbb16637d6eed8524a06bc2053e. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: coactions/setup-xvfb@b6b4fcfb9f5a895edadc3bc76318fae0ac17c8b3. 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: Sibz/github-status-action@071b5370da85afbb16637d6eed8524a06bc2053e, bobheadxi/deployments@88ce5600046c82542f8246ac287d0a53c461bca3, actions/github-script@v6, nwtgck/actions-netlify@7a92f00dde8c92a5a9e8385ec2919775f7647352. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

[Rust Crypto] › read-receipts/redactions.spec.ts took 6.3m

[Legacy Crypto] › read-receipts/redactions.spec.ts took 5.3m

[Rust Crypto] › read-receipts/new-messages.spec.ts took 3.8m

[Rust Crypto] › read-receipts/high-level.spec.ts took 3.7m

[Legacy Crypto] › read-receipts/new-messages.spec.ts took 3.5m