1) [Chrome] › playwright/e2e/settings/room-settings/room-security-tab.spec.ts:81:5 › Roles & Permissions room settings tab › should disallow changing from public to private if the user cannot alter history @screenshot Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.blur: Test timeout of 30000ms exceeded. Call log: - waiting for locator('.mx_Dialog').filter({ has: locator('.mx_RoomSettingsDialog') }).getByRole('spinbutton', { name: '@user_6496a26110e4309860ce-e6b187015ed0865317ce:localhost' }) 101 | const ourPl = settings.getByRole("spinbutton", { name: user.userId }); 102 | await ourPl.fill("80"); > 103 | await ourPl.blur(); // Shows a warning on | ^ 104 | 105 | // Accept the de-op 106 | await page.getByRole("button", { name: "Continue" }).click(); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/settings/room-settings/room-security-tab.spec.ts:103:25

1) [Chrome] › playwright/e2e/settings/room-settings/room-security-tab.spec.ts:81:5 › Roles & Permissions room settings tab › should disallow changing from public to private if the user cannot alter history @screenshot Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

1) [Chrome] › playwright/e2e/settings/room-settings/room-security-tab.spec.ts:81:5 › Roles & Permissions room settings tab › should disallow changing from public to private if the user cannot alter history @screenshot Error: locator.blur: Test timeout of 30000ms exceeded. Call log: - waiting for locator('.mx_Dialog').filter({ has: locator('.mx_RoomSettingsDialog') }).getByRole('spinbutton', { name: '@user_6496a26110e4309860ce-e6b187015ed0865317ce:localhost' }) - locator resolved to <input max="100" value="100" type="number" id="mx_Field_5" label="@user_6496a26110e4309860ce-e6b187015ed0865317ce:localhost" placeholder="@user_6496a26110e4309860ce-e6b187015ed0865317ce:localhost"/> - element was detached from the DOM, retrying 101 | const ourPl = settings.getByRole("spinbutton", { name: user.userId }); 102 | await ourPl.fill("80"); > 103 | await ourPl.blur(); // Shows a warning on | ^ 104 | 105 | // Accept the de-op 106 | await page.getByRole("button", { name: "Continue" }).click(); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/settings/room-settings/room-security-tab.spec.ts:103:25

1) [Chrome] › playwright/e2e/settings/room-settings/room-security-tab.spec.ts:81:5 › Roles & Permissions room settings tab › should disallow changing from public to private if the user cannot alter history @screenshot Test timeout of 30000ms exceeded.

3) [Chrome] › playwright/e2e/sliding-sync/sliding-sync.spec.ts:225:5 › Sliding Sync › should show and be able to accept/reject/rescind invites Error: expect(locator).toHaveText(expected) failed Locator: getByTestId('room-list').getByTestId('room-name') Timeout: 5000ms - Expected - 1 + Received + 1 Array [ - "Room to Rescind", "Room to Reject", + "Room to Rescind", ] Call log: - Expect "toHaveText" with timeout 5000ms - waiting for getByTestId('room-list').getByTestId('room-name') 3 × locator resolved to 3 elements 6 × locator resolved to 2 elements 39 | test.describe("Sliding Sync", () => { 40 | const checkOrder = async (wantOrder: string[], page: Page) => { > 41 | await expect(page.getByTestId("room-list").getByTestId("room-name")).toHaveText(wantOrder); | ^ 42 | }; 43 | 44 | const bumpRoom = async (roomId: string, app: ElementAppPage) => { at checkOrder (/home/runner/work/element-web/element-web/apps/web/playwright/e2e/sliding-sync/sliding-sync.spec.ts:41:78) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/sliding-sync/sliding-sync.spec.ts:259:15

2) [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:179:9 › OIDC Native › with force_verification on › continues to show verification prompt after cancelling device verification @no-firefox @no-webkit @screenshot Error: locator.click: Test timeout of 90000ms exceeded. Call log: - waiting for getByRole('button', { name: 'Start' }) - locator resolved to <button tabindex="0" role="button" data-size="md" data-kind="secondary" class="_button_1nw83_8 _has-icon_1nw83_60">…</button> - 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">…</div> from <div id="mx_Dialog_StaticContainer">…</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">…</div> from <div id="mx_Dialog_StaticContainer">…</div> subtree intercepts pointer events - retrying click action - waiting 100ms 165 × 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">…</div> from <div id="mx_Dialog_StaticContainer">…</div> subtree intercepts pointer events - retrying click action - waiting 500ms 241 | await deviceToVerifyPage.getByRole("button", { name: "Use another device" }).click(); 242 | await alreadyVerifiedDevicePage.getByRole("button", { name: "Start verification" }).click(); > 243 | await alreadyVerifiedDevicePage.getByRole("button", { name: "Start" }).click(); | ^ 244 | await alreadyVerifiedDevicePage.getByRole("button", { name: "They match" }).click(); 245 | await deviceToVerifyPage.getByRole("button", { name: "They match" }).click(); 246 | await alreadyVerifiedDevicePage.getByRole("button", { name: "Got it" }).click(); at verifyUsingOtherDevice (/home/runner/work/element-web/element-web/apps/web/playwright/e2e/oidc/oidc-native.spec.ts:243:76) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/oidc/oidc-native.spec.ts:201:17

2) [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:179:9 › OIDC Native › with force_verification on › continues to show verification prompt after cancelling device verification @no-firefox @no-webkit @screenshot Test timeout of 90000ms 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

1) [Chrome] › playwright/e2e/audio-player/audio-player.spec.ts:263:5 › Audio player › should support creating a reply chain with multiple audio files @no-firefox @no-webkit @screenshot Error: Test timeout of 90000ms exceeded 20 | await tile.hover(); 21 | await tile.getByRole("button", { name: "Reply", exact: true }).click(); > 22 | }).toPass(); | ^ 23 | await expect(tile.page().getByText("Replying", { exact: true })).toBeVisible(); 24 | }; 25 | at clickButtonReply (/home/runner/work/element-web/element-web/apps/web/playwright/e2e/audio-player/audio-player.spec.ts:22:8) at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/audio-player/audio-player.spec.ts:291:19

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/

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/

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/

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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756, 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 (19.9s)

1 skipped 6 passed (19.8s)

1 skipped 6 passed (19.4s)

33 skipped 124 passed (12.6m)

1 skipped 6 passed (18.4s)

1 skipped 6 passed (19.6s)

1 flaky [Chrome] › playwright/e2e/settings/room-settings/room-security-tab.spec.ts:81:5 › Roles & Permissions room settings tab › should disallow changing from public to private if the user cannot alter history @screenshot 15 skipped 157 passed (16.0m)

1 skipped 6 passed (25.4s)

3 flaky [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 [Chrome] › playwright/e2e/oidc/oidc-native.spec.ts:179:9 › OIDC Native › with force_verification on › continues to show verification prompt after cancelling device verification @no-firefox @no-webkit @screenshot [Chrome] › playwright/e2e/sliding-sync/sliding-sync.spec.ts:225:5 › Sliding Sync › should show and be able to accept/reject/rescind invites 2 skipped 164 passed (19.0m)

1 flaky [Chrome] › playwright/e2e/audio-player/audio-player.spec.ts:263:5 › Audio player › should support creating a reply chain with multiple audio files @no-firefox @no-webkit @screenshot 188 passed (20.3m)

1 skipped 6 passed (25.4s)