1) [chromium] › specs/restricted-meeting.spec.ts:38:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.

1) [chromium] › specs/restricted-meeting.spec.ts:38:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: 'Waiting to be admitted' }) Expected: visible Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 60000ms - waiting for getByRole('heading', { name: 'Waiting to be admitted' }) 58 | await expect( 59 | guest.page.getByRole("heading", { name: "Waiting to be admitted" }), > 60 | ).toBeVisible({ timeout: lobbyTransitionTimeout }); | ^ 61 | 62 | await hostPage.getByTestId("toolbar-people").click(); 63 | await expect(hostPage.getByTestId("people-panel")).toBeVisible(); at /home/runner/work/meet/meet/e2e/specs/restricted-meeting.spec.ts:60:5

1) [chromium] › specs/restricted-meeting.spec.ts:38:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected 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 16th, 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/