2) [Chrome] › playwright/e2e/timeline/timeline.spec.ts:1077:9 › Timeline › message sending › should display a reply chain @no-firefox @no-webkit @screenshot Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx_EventTile_last') 41 pixels (ratio 0.01 of all image pixels) are different. Snapshot: event-tile-reply-chains-irc-modern.png Call log: - Expect "toHaveScreenshot(event-tile-reply-chains-irc-modern.png)" 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" aria-atomic="true" data-layout="group" data-has-reply="true" data-event-id="$H6ZD_9QyCaV_tXdsVx_O-CLE_nahWO3N_RhXeMQA5nU" data-scroll-tokens="$H6ZD_9QyCaV_tXdsVx_O-CLE_nahWO3N_RhXeMQA5nU" class="mx_EventTile mx_EventTile_continuation mx_EventTile_last mx_EventTile_lastInSection">…</li> - 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 - 41 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" aria-atomic="true" data-layout="group" data-has-reply="true" data-event-id="$H6ZD_9QyCaV_tXdsVx_O-CLE_nahWO3N_RhXeMQA5nU" data-scroll-tokens="$H6ZD_9QyCaV_tXdsVx_O-CLE_nahWO3N_RhXeMQA5nU" class="mx_EventTile mx_EventTile_continuation mx_EventTile_last mx_EventTile_lastInSection">…</li> - 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 - 41 pixels (ratio 0.01 of all image pixels) are different. 1162 | 1163 | // Take a snapshot on modern layout > 1164 | await expect(page.locator(".mx_EventTile_last")).toMatchScreenshot( | ^ 1165 | "event-tile-reply-chains-irc-modern.png", 1166 | screenshotOptions, 1167 | ); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/timeline/timeline.spec.ts:1164:62

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 identity') Expected: visible Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for getByText('Confirm your identity') 132 | 133 | // We should be in > 134 | await expect(page.getByText("Confirm your 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:63

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/