1) [Chrome] › playwright/e2e/timeline/timeline.spec.ts:232:9 › Timeline › configure room › should click 'collapse' on the first hovered info event line inside GELS on bubble layout @screenshot Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx_MainSplit') 214 pixels (ratio 0.01 of all image pixels) are different. Snapshot: expanded-gels-bubble-layout.png Call log: - Expect "toHaveScreenshot(expanded-gels-bubble-layout.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx_MainSplit') - locator resolved to <div class="mx_MainSplit">…</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 - 214 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx_MainSplit') - locator resolved to <div class="mx_MainSplit">…</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 - 214 pixels (ratio 0.01 of all image pixels) are different. 258 | 259 | // Save snapshot of expanded generic event list summary on bubble layout > 260 | await expect(page.locator(".mx_MainSplit")).toMatchScreenshot("expanded-gels-bubble-layout.png", { | ^ 261 | // Exclude timestamp from snapshot 262 | css: ` 263 | .mx_MessageTimestamp { at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/timeline/timeline.spec.ts:260:61

2) [Chrome] › playwright/e2e/crypto/toasts.spec.ts:35: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. 40 | // Mask the background of the screenshot to avoid failing the test just because some 41 | // other component have changed its rendering. > 42 | await expect(page.getByRole("alert").first()).toMatchScreenshot("key-storage-out-of-sync-toast.png", { | ^ 43 | css: ` 44 | .mx_ToastContainer { 45 | background-color: magenta !important; at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/crypto/toasts.spec.ts:42:55

1) [Chrome] › playwright/e2e/accessibility/keyboard-navigation.spec.ts:106:5 › Landmark navigation tests › without an open room Error: expect(locator).toBeFocused() failed Locator: locator('.mx_HomePage') Expected: focused Received: inactive Timeout: 5000ms Call log: - Expect "toBeFocused" with timeout 5000ms - waiting for locator('.mx_HomePage') 7 × locator resolved to <main tabindex="-1" class="mx_AutoHideScrollbar mx_HomePage mx_HomePage_default">…</main> - unexpected value "inactive" 140 | // Pressing Control+F6 again will focus the home section 141 | await page.keyboard.press("ControlOrMeta+F6"); > 142 | await expect(page.locator(".mx_HomePage")).toBeFocused(); | ^ 143 | 144 | // Pressing Control+F6 will bring focus back to the space button 145 | await page.keyboard.press("ControlOrMeta+F6"); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/accessibility/keyboard-navigation.spec.ts:142:52

1) [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:82:5 › OIDC Native › it should log out the user & wipe data when logging out via MAS @no-firefox @no-webkit @screenshot Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 21 Received array: ["react_sdk_session_lock_owner", "mx_local_settings", "mx_has_access_token", "mx_oidc_client_id", "mx_oidc_token_issuer", "must_verify_device", "mx_draft_cleanup", "mx_profile_displayname", "mx_device_id", "mx_has_refresh_token", …] 104 | 105 | const localStorageKeys = await page.evaluate(() => Object.keys(localStorage)); > 106 | expect(localStorageKeys).toHaveLength(0); | ^ 107 | }, 108 | ); 109 | at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/oidc/oidc-native.spec.ts:106:38

1) [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:82:5 › OIDC Native › it should log out the user & wipe data when logging out via MAS @no-firefox @no-webkit @screenshot Error: expect(received).toHaveLength(expected) Expected length: 0 Received length: 21 Received array: ["react_sdk_session_lock_owner", "mx_local_settings", "mx_has_access_token", "mx_oidc_client_id", "mx_oidc_token_issuer", "must_verify_device", "mx_draft_cleanup", "mx_profile_displayname", "mx_device_id", "mx_has_refresh_token", …] 104 | 105 | const localStorageKeys = await page.evaluate(() => Object.keys(localStorage)); > 106 | expect(localStorageKeys).toHaveLength(0); | ^ 107 | }, 108 | ); 109 | at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/oidc/oidc-native.spec.ts:106:38

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

3 skipped 84 passed (5.5m)

76 passed (6.1m)

82 passed (8.6m)

1 flaky [Chrome] › playwright/e2e/timeline/timeline.spec.ts:232:9 › Timeline › configure room › should click 'collapse' on the first hovered info event line inside GELS on bubble layout @screenshot 2 skipped 91 passed (8.9m)

2 flaky [Chrome] › playwright/e2e/accessibility/keyboard-navigation.spec.ts:106:5 › Landmark navigation tests › without an open room [Chrome] › playwright/e2e/crypto/toasts.spec.ts:35:5 › Key storage out of sync toast › should prompt for recovery key if 'enter recovery key' pressed @screenshot 87 passed (9.3m)