Skip to content

Update to llama command #26

Update to llama command

Update to llama command #26

Triggered via pull request May 21, 2026 05:24
Status Failure
Total duration 2m 44s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Run tests
Process completed with exit code 1.
[client (chromium)] tests/unit/page.svelte.spec.ts > +page.svelte > copies install command and toggles icon after click: tests/unit/page.svelte.spec.ts#L42
AssertionError: expected "vi.fn()" to be called with arguments: [ Array(1) ] Received: 1st vi.fn() call: [ - "curl -LsSf https://llama.app/install.sh | bash", + "curl -LsSf https://llama.app/install.sh | sh", ] Number of calls: 1 ❯ tests/unit/page.svelte.spec.ts:42:20
[client (chromium)] tests/unit/page.svelte.spec.ts > +page.svelte > renders install command and package manager link: tests/unit/page.svelte.spec.ts#L12
VitestBrowserElementError: Cannot find element with locator: getByText('curl -LsSf https://llama.app/install.sh | bash') <body> <div> <main class="mx-auto w-full max-w-5xl px-8 md:px-16" > <header … /> <!----> <section … /> <section … /> <section … /> <section … /> <section … /> </main> </div> </body>... ❯ tests/unit/page.svelte.spec.ts:12:56 Caused by: Caused by: Error: Matcher did not succeed in time. ❯ Module.track_reactivity_loss node_modules/svelte/src/internal/client/reactivity/async.js:167:13 ❯ tests/unit/page.svelte.spec.ts:13:4
Run tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@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/