1) [chromium] › specs/multi-participant.spec.ts:4:6 › Multi participant › host and two guests see the same meeting Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: page.goto: Target page, context or browser has been closed at ../fixtures/test.ts:121 119 | }, 120 | async joinAsGuest(meetingId: string, guestName: string) { > 121 | await page.goto(`/meet/${meetingId}`); | ^ 122 | await expect(page.getByTestId("meeting-preview")).toBeVisible({ 123 | timeout: previewTimeout, 124 | }); at Object.joinAsGuest (/home/runner/work/meet/meet/e2e/fixtures/test.ts:121:15) at /home/runner/work/meet/meet/e2e/specs/multi-participant.spec.ts:11:18

1) [chromium] › specs/multi-participant.spec.ts:4:6 › Multi participant › host and two guests see the same meeting Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.

1) [chromium] › specs/multi-participant.spec.ts:4:6 › Multi participant › host and two guests see the same meeting Error: locator.waitFor: Target page, context or browser has been closed Call log: - waiting for getByTestId('meeting-layout') to be visible at ../fixtures/test.ts:47 45 | 46 | async function waitForMeetingReady(page: Page): Promise<void> { > 47 | await page.getByTestId("meeting-layout").waitFor({ | ^ 48 | state: "visible", 49 | timeout: meetingReadyTimeout, 50 | }); at waitForMeetingReady (/home/runner/work/meet/meet/e2e/fixtures/test.ts:47:43) at joinFromPreview (/home/runner/work/meet/meet/e2e/fixtures/test.ts:82:8) at Object.joinAsGuest (/home/runner/work/meet/meet/e2e/fixtures/test.ts:131:4) at /home/runner/work/meet/meet/e2e/specs/multi-participant.spec.ts:11:3

1) [chromium] › specs/multi-participant.spec.ts:4:6 › Multi participant › host and two guests see the same meeting Test timeout of 60000ms exceeded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/setup-python@v5. 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/