1) [Chrome] › playwright/e2e/crypto/decryption-failure-messages.spec.ts:33:9 › Cryptography › decryption failure messages › should handle device-relative historical messages @screenshot Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('room-list').locator('[title="Test room"]').first() - locator resolved to <div title="Test room" data-testid="room-name" class="_roomName_rtaba_83">Test room</div> - attempting click action 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="mx_Dialog_background" data-testid="dialog-background"></div> from <div id="mx_Dialog_Container">…</div> subtree intercepts pointer events - retrying click action - waiting 20ms 2 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="mx_Dialog_background" data-testid="dialog-background"></div> from <div id="mx_Dialog_Container">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 110 × waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <div class="mx_Dialog_background" data-testid="dialog-background"></div> from <div id="mx_Dialog_Container">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms at ../pages/ElementAppPage.ts:97 95 | public async viewRoomByName(name: string): Promise<void> { 96 | // We get the room list by test-id which is a listbox and matching title=name > 97 | return this.page.getByTestId("room-list").locator(`[title="${name}"]`).first().click(); | ^ 98 | } 99 | 100 | /** at ElementAppPage.viewRoomByName (/home/runner/work/element-web/element-web/apps/web/playwright/pages/ElementAppPage.ts:97:88) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/crypto/decryption-failure-messages.spec.ts:50:27

1) [Chrome] › playwright/e2e/crypto/decryption-failure-messages.spec.ts:33:9 › Cryptography › decryption failure messages › should handle device-relative historical messages @screenshot Test timeout of 60000ms exceeded.

1) [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:110:5 › OIDC Native › can log in to an existing MAS account @no-firefox @no-webkit @screenshot Error: expect(locator).toBeVisible() failed Locator: getByText('Confirm your digital identity') Expected: visible Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for getByText('Confirm your digital identity') 132 | 133 | // We should be in > 134 | await expect(page.getByText("Confirm your digital identity")).toBeVisible(); | ^ 135 | }); 136 | 137 | test.describe("with force_verification on", () => { at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/oidc/oidc-native.spec.ts:134:71

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/

1 skipped 6 passed (24.5s)

1 skipped 130 passed (10.4m)

3 skipped 130 passed (11.2m)

1 flaky [Chrome] › playwright/e2e/crypto/decryption-failure-messages.spec.ts:33:9 › Cryptography › decryption failure messages › should handle device-relative historical messages @screenshot 134 passed (13.7m)