chore: remove agent instructions file #96
Annotations
3 errors, 1 warning, and 1 notice
|
[chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected:
e2e/specs/restricted-meeting.spec.ts#L71
1) [chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: locator.click: Target page, context or browser has been closed
Call log:
- waiting for getByTestId('join-meeting-preview-button')
- locator resolved to <button type="submit" data-testid="join-meeting-preview-button" class="w-full inline-flex items-center justify-center gap-2 transition-colors focus:outline-none shrink-0 text-ink-white bg-surface-gray-7 hover:bg-surface-gray-6 active:bg-surface-gray-5 focus-visible:ring focus-visible:ring-outline-gray-3 h-10 text-lg font-medium px-3 rounded-md">…</button>
- attempting click action
- waiting for element to be visible, enabled and stable
69 | await guest.page.goto(`/meet/${meetingId}`);
70 | await expect(guest.page.getByTestId("meeting-preview")).toBeVisible();
> 71 | await guest.page.getByTestId("join-meeting-preview-button").click();
| ^
72 |
73 | await expect(
74 | guest.page.getByRole("heading", { name: "Waiting to be admitted" }),
at /home/runner/work/meet/meet/e2e/specs/restricted-meeting.spec.ts:71:63
|
|
[chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected:
e2e/specs/restricted-meeting.spec.ts#L0
1) [chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Test timeout of 60000ms exceeded.
|
|
[chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected:
e2e/specs/restricted-meeting.spec.ts#L54
1) [chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected
Error: expect(locator).toBeVisible() failed
Locator: getByText('Waiting to be admitted')
Expected: visible
Timeout: 10000ms
Error: element(s) not found
Call log:
- Expect "toBeVisible" with timeout 10000ms
- waiting for getByText('Waiting to be admitted')
52 | await guest.page.getByTestId("join-meeting-preview-button").click();
53 |
> 54 | await expect(guest.page.getByText("Waiting to be admitted")).toBeVisible();
| ^
55 |
56 | await hostPage.getByTestId("toolbar-people").click();
57 | await expect(hostPage.getByTestId("people-panel")).toBeVisible();
at /home/runner/work/meet/meet/e2e/specs/restricted-meeting.spec.ts:54:64
|
|
E2E Tests
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/
|
|
🎭 Playwright Run Summary
1 flaky
[chromium] › specs/restricted-meeting.spec.ts:34:6 › Restricted meeting › guest in restricted lobby can't join meeting when rejected
11 passed (6.8m)
|