Process completed with exit code 1.

1) [chromium] › tests/announcement-and-ssh-keys.spec.ts:10:7 › Announcement and SSH Keys › what's new dialog appears once for authenticated users Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: 'Request Access is now AET Request.' }) Expected: visible Timeout: 10000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 10000ms - waiting for getByRole('heading', { name: 'Request Access is now AET Request.' }) 21 | page.getByRole("heading", { 22 | name: "Request Access is now AET Request." }), > 23 | ).toBeVisible(); | ^ 24 | await expect(page.getByText("Coming soon")).toBeVisible(); 25 | 26 | await page.getByRole("button", { name: "Continue" }).click(); at /home/runner/work/request/request/e2e/tests/announcement-and-ssh-keys.spec.ts:23:7

1) [chromium] › tests/announcement-and-ssh-keys.spec.ts:10:7 › Announcement and SSH Keys › what's new dialog appears once for authenticated users Error: expect(locator).toBeVisible() failed Locator: getByRole('heading', { name: 'Request Access is now AET Request.' }) Expected: visible Timeout: 10000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 10000ms - waiting for getByRole('heading', { name: 'Request Access is now AET Request.' }) 21 | page.getByRole("heading", { 22 | name: "Request Access is now AET Request." }), > 23 | ).toBeVisible(); | ^ 24 | await expect(page.getByText("Coming soon")).toBeVisible(); 25 | 26 | await page.getByRole("button", { name: "Continue" }).click(); at /home/runner/work/request/request/e2e/tests/announcement-and-ssh-keys.spec.ts:23:7

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/