2) [chromium] › specs/host-controls.spec.ts:4:6 › Host controls › host can mute a guest participant Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect.toBeVisible: Target page, context or browser has been closed at ../fixtures/test.ts:51 49 | timeout: meetingReadyTimeout, 50 | }); > 51 | await expect(page.getByTestId("meeting-toolbar")).toBeVisible(); | ^ 52 | await expect(page.getByTestId("toolbar-end-call")).toBeVisible(); 53 | } 54 | at waitForMeetingReady (/home/runner/work/meet/meet/e2e/fixtures/test.ts:51:52) at joinFromPreview (/home/runner/work/meet/meet/e2e/fixtures/test.ts:82:2) at Object.joinAsGuest (/home/runner/work/meet/meet/e2e/fixtures/test.ts:131:4) at /home/runner/work/meet/meet/e2e/specs/host-controls.spec.ts:10:3

2) [chromium] › specs/host-controls.spec.ts:4:6 › Host controls › host can mute a guest participant Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.

2) [chromium] › specs/host-controls.spec.ts:4:6 › Host controls › host can mute a guest participant Error: locator.click: Target page, context or browser has been closed Call log: - waiting for locator('[data-testid^=\'participant-tile-\']').filter({ hasText: 'Guest Mute 0' }).first().getByRole('button', { name: 'Mute participant' }) 17 | await expect(guestTileOnHost).toBeVisible(); 18 | await guestTileOnHost.hover(); > 19 | await guestTileOnHost.getByRole("button", { name: "Mute participant" }).click(); | ^ 20 | 21 | await expect(guestTileOnHost).toHaveAttribute("data-audio-enabled", "false"); 22 | await expect( at /home/runner/work/meet/meet/e2e/specs/host-controls.spec.ts:19:75

2) [chromium] › specs/host-controls.spec.ts:4:6 › Host controls › host can mute a guest participant Test timeout of 60000ms exceeded.

1) [chromium] › specs/engagement.spec.ts:4:6 › Reactions and raise hand › guest reaction and raised hand are visible to the host Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 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/engagement.spec.ts:9:3

1) [chromium] › specs/engagement.spec.ts:4:6 › Reactions and raise hand › guest reaction and raised hand are visible to the host Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.

1) [chromium] › specs/engagement.spec.ts:4:6 › Reactions and raise hand › guest reaction and raised hand are visible to the host Error: locator.click: Target page, context or browser has been closed Call log: - waiting for getByLabel('Send 👍 reaction') - locator resolved to <button type="button" data-testid="reaction-👍" aria-label="Send 👍 reaction" class="mx-auto flex items-center justify-center w-12 h-12 rounded-full bg-white/10 hover:bg-white/20 transition-colors text-2xl">👍</button> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed 10 | 11 | await guest.page.getByTestId("toolbar-reactions").click(); > 12 | await guest.page.getByLabel("Send 👍 reaction").click(); | ^ 13 | 14 | await expect(hostPage.locator("[aria-label^='Reaction 👍']")).toBeVisible(); 15 | at /home/runner/work/meet/meet/e2e/specs/engagement.spec.ts:12:51

1) [chromium] › specs/engagement.spec.ts:4:6 › Reactions and raise hand › guest reaction and raised hand are visible to the host 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/