1) [Chrome] › playwright/e2e/settings/encryption-user-tab/encryption-tab.spec.ts:35:9 › Encryption tab › when encryption is set up › should show a 'Verify this device' button if the device is unverified @screenshot Error: expect(locator).toHaveScreenshot(expected) failed Locator: getByTestId('encryptionTab') 73979 pixels (ratio 0.10 of all image pixels) are different. Snapshot: default-tab.png Call log: - Expect "toHaveScreenshot(default-tab.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for getByTestId('encryptionTab') - locator resolved to <div data-testid="encryptionTab" class="mx_SettingsTab mx_EncryptionUserSettingsTab">…</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 - 73978 pixels (ratio 0.10 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for getByTestId('encryptionTab') - locator resolved to <div data-testid="encryptionTab" class="mx_SettingsTab mx_EncryptionUserSettingsTab">…</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 - 73979 pixels (ratio 0.10 of all image pixels) are different. 48 | await util.verifyDevice(recoveryKey); 49 | > 50 | await expect(content).toMatchScreenshot("default-tab.png", { | ^ 51 | mask: [content.getByTestId("deviceId"), content.getByTestId("sessionKey")], 52 | }); 53 | at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/settings/encryption-user-tab/encryption-tab.spec.ts:50:39

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The process '/Users/runner/setup-pnpm/node_modules/.bin/pnpm' failed with exit code 254

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The process '/usr/bin/xvfb-run' failed with exit code 254

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The operation was canceled.

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The operation was canceled.

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The operation was canceled.

1) [Chrome] › playwright/e2e/crypto/toasts.spec.ts:45: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. 48 | // it would always be checking the same toast, even if another one is now the first. 49 | await expect(page.getByRole("alert")).toHaveCount(2); > 50 | await expect(page.getByRole("alert").first()).toMatchScreenshot( | ^ 51 | "key-storage-out-of-sync-toast.png", 52 | screenshotOptions, 53 | ); at /home/runner/work/element-web/element-web/apps/web/playwright/e2e/crypto/toasts.spec.ts:50:55

The process 'C:\Users\runneradmin\setup-pnpm\node_modules\.bin\pnpm.CMD' failed with exit code 1

The strategy configuration was canceled because "build_ed_windows.ia32" failed

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The operation was canceled.

The strategy configuration was canceled because "build_ed_windows.ia32" failed

No files were found with the provided path: apps/desktop/blob-report. No artifacts will be uploaded.

The operation was canceled.

Process completed with exit code 1.

The strategy configuration was canceled because "build_ed_windows.ia32" failed

The strategy configuration was canceled because "build_ed_windows.ia32" failed

The strategy configuration was canceled because "build_ed_windows.ia32" failed

The strategy configuration was canceled because "build_ed_windows.ia32" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

The strategy configuration was canceled because "build_ed_linux.system_arm64" failed

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: maxim-lobanov/setup-xcode@60606e260d2fc5762a71e64e74b2174e8ea3c8bd. 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: 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. 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: coactions/setup-xvfb@6b00cf1889f4e1d5a48635647013c0508128ee1a. 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: coactions/setup-xvfb@6b00cf1889f4e1d5a48635647013c0508128ee1a. 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. 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. 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. 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: coactions/setup-xvfb@6b00cf1889f4e1d5a48635647013c0508128ee1a. 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: coactions/setup-xvfb@6b00cf1889f4e1d5a48635647013c0508128ee1a. 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.8m)

1 flaky [Chrome] › playwright/e2e/settings/encryption-user-tab/encryption-tab.spec.ts:35:9 › Encryption tab › when encryption is set up › should show a 'Verify this device' button if the device is unverified @screenshot 79 passed (6.9m)

84 passed (8.5m)

1 flaky [Chrome] › playwright/e2e/crypto/toasts.spec.ts:45:5 › Key storage out of sync toast › should prompt for recovery key if 'enter recovery key' pressed @screenshot 89 passed (8.9m)

2 skipped 94 passed (9.0m)