1) [Chrome] › playwright/e2e/crypto/crypto.spec.ts:229:9 › Cryptography › should allow verification when there is no existing DM Test timeout of 30000ms exceeded.

1) [Chrome] › playwright/e2e/crypto/crypto.spec.ts:229:9 › Cryptography › should allow verification when there is no existing DM Error: jsHandle.evaluateHandle: Test timeout of 30000ms exceeded. at ../pages/client.ts:82 80 | public async evaluateHandle<T>(fn: (client: MatrixClient) => T, arg?: any): Promise<JSHandle<T>> { 81 | await this.prepareClient(); > 82 | return this.client.evaluateHandle(fn, arg); | ^ 83 | } 84 | 85 | /** at Bot.evaluateHandle (/home/runner/work/element-web/element-web/playwright/pages/client.ts:82:28)

1) [Chrome] › playwright/e2e/crypto/crypto.spec.ts:229:9 › Cryptography › should allow verification when there is no existing DM Error: locator.click: Test timeout of 30000ms exceeded. Call log: - waiting for locator('.mx_RightPanel').getByRole('button', { name: 'Verify by emoji' }) at crypto/utils.ts:448 446 | 447 | // this requires creating a DM, so can take a while. Give it a longer timeout. > 448 | await roomInfo.getByRole("button", { name: "Verify by emoji" }).click({ timeout: 30000 }); | ^ 449 | 450 | const request = await bobsVerificationRequestPromise; 451 | // the bot user races with the Element user to hit the "verify by emoji" button at verify (/home/runner/work/element-web/element-web/playwright/e2e/crypto/utils.ts:448:69) at /home/runner/work/element-web/element-web/playwright/e2e/crypto/crypto.spec.ts:240:9

2) [Chrome] › playwright/e2e/crypto/device-verification.spec.ts:121:9 › Device verification › Verify device with QR code during login @no-webkit Error: "route.fetch: Test ended." while running route callback. Consider awaiting `await page.unrouteAll({ behavior: 'ignoreErrors' })` before the end of the test to ignore remaining routes in flight. 94 | await route.fulfill({ json: {} }); 95 | await new Promise((f) => setTimeout(f, 1000)); > 96 | await route.fetch(); | ^ 97 | }); 98 | 99 | await logIntoElement(page, credentials); at /home/runner/work/element-web/element-web/playwright/e2e/crypto/device-verification.spec.ts:96:25

2) [Chrome] › playwright/e2e/crypto/device-verification.spec.ts:121:9 › Device verification › Verify device with QR code during login @no-webkit Error: apiRequestContext.fetch: Target page, context or browser has been closed Call log: - → POST http://localhost:40711/_synapse/admin/v1/register - user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.6998.35 Safari/537.36 - accept: */* - accept-encoding: gzip,deflate,br - content-type: application/json - content-length: 308 at ../plugins/utils/api.ts:27 25 | public async request<R extends {}>(verb: Verb, path: string, token?: string, data?: object): Promise<R> { 26 | const url = `${this.baseUrl}${path}`; > 27 | const res = await this._request.fetch(url, { | ^ 28 | data, 29 | method: verb, 30 | headers: token at Api.request (/home/runner/work/element-web/element-web/playwright/plugins/utils/api.ts:27:41) at StartedSynapseContainer.registerUserInternal (/home/runner/work/element-web/element-web/playwright/testcontainers/synapse.ts:307:42) at Object.credentials (/home/runner/work/element-web/element-web/playwright/element-web-test.ts:162:29)